Switched highAvailability mode to true as new default #811
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The
highAvailability
flag in thevalues.yaml
file in the helm charts is switched to true, which should be the default for now.How can this be tested?
Simply switch to this branch, run make manifests and take a look at the
kubernetes.yaml
. Apply it and check for the changed things liketopologySpreadConstraints
in the webhook deployment and so on.Checklist