-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Automated cherry pick of #16670: Fix cluster-autoscaler priority expander config #16673
Automated cherry pick of #16670: Fix cluster-autoscaler priority expander config #16673
Conversation
We were iterating over a map which has undefined ordering, resulting in inconsistent diffs to the manifest during `kops update cluster`. We now sort the instsance groups to ensure the rendered manifest remains consistent.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
/retest |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
2 similar comments
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
/hold |
/unhold |
Cherry pick of #16670 on release-1.28.
#16670: Fix cluster-autoscaler priority expander config
For details on the cherry pick process, see the cherry pick requests page.