-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix cluster-autoscaler addon #13202
fix cluster-autoscaler addon #13202
Conversation
/approve |
LGTM label has been added. Git tree hash: 3f3784421c6d015591e9e5b9eef043b5a8f8ec98
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kron4eg, xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherrypick release/v2.25 |
@xrstf: once the present PR merges, I will cherry-pick it on top of release/v2.25 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherrypick release/v2.24 |
@xrstf: once the present PR merges, I will cherry-pick it on top of release/v2.24 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherrypick release/v2.23 |
@xrstf: once the present PR merges, I will cherry-pick it on top of release/v2.23 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@xrstf: new pull request created: #13203 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@xrstf: #13202 failed to apply on top of branch "release/v2.24":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@xrstf: #13202 failed to apply on top of branch "release/v2.23":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What this PR does / why we need it:
After updating the autoscaler on one of our dev systems, I noticed that the cluster-name based grouping didn't work. And from my quick testing, creating an AWS cluster on dev and installing the autoscaler addon will not work. So I adjusted the config to match what we use in our other system, which @xmudrii recommended to me. Downside is that it will only work for MDs in the kube-system namespace.
I also removed the master toleration. There are no master nodes in a KKP usercluster.
What type of PR is this?
/kind bug
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: