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
feat(clusterapi): per nodeGroup autoscaling options #6743
base: master
Are you sure you want to change the base?
Conversation
Hi @mweibel. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mweibel The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ping @elmiko - maybe you have some time to review this other PR of mine. Thanks :) or give /ok-to-test would also be nice 👍 |
apologies @mweibel /ok-to-test |
this seems like a cool feature, i need some time to study the PR |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Implements overrding of autoscaling options per NodeGroup (MachineDeployment/Set/Pool). This allows us to improve scale up/down behavior depending on the node groups configuration.
Which issue(s) this PR fixes:
Fixes #6742
Special notes for your reviewer:
The annotation prefix is intentionally does not contain
cluster-api-autoscaler-node-group-
after the slash because the annotation key must be less than 63 chars long.Does this PR introduce a user-facing change?