Rework control plane policies #647
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-project-automation
bot
moved this from In progress
to Done
in kubernetes-controller-sharding
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
For the evaluation in my Master's thesis, I had a dedicated Gardener environment. Also, a lot has changed in the area of control plane stability and auto-scaling in Gardener since then.
This PR reworks the control plane policies to revive the load test experiments on my SKE test setup.
I figured I could spare the kyverno hustle by simply setting
minReplicas=maxReplicasin the kube-apiserver HPA. So this PR removes a lot of pain I had with the previous control plane policies.Which issue(s) this PR fixes:
Fixes n/a
Special notes for your reviewer: