-
Notifications
You must be signed in to change notification settings - Fork 4k
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
expand CAPI_GROUP usage to cover other capi group variables #4451
Conversation
/assign @enxebre |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elmiko 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 |
361f3c1
to
c726da7
Compare
slightly related I created #4453 |
yeah, i can clean those up as well. i was mainly focused on the min/max annotations, but i think it makes sense to set all of these. |
This change updates the logic for the clusterapi autoscaler provider so that the `CAPI_GROUP` environment variable will also affect the annotations keys for minimum and maximum node group size, the machine annotation, machine deletion, and the cluster name label. It also addes unit tests and an update to the readme.
c726da7
to
755cb1b
Compare
update
|
this is mostly a lgtm from me, but defer to @enxebre for final lgtm. |
/lgtm |
@elmiko although changing the group is recommended only for testing purposes this is technically a breaking change for the annotations we are now including within the swappable apigroup. Please let's make sure we include a proper release note. |
ack, thanks for the heads up @enxebre |
This change updates the logic for the clusterapi autoscaler provider so
that the
CAPI_GROUP
environment variable will also affect theannotations keys for minimum and maximum node group size, the machine
annotation, machine deletion, and the cluster name label. It also addes
unit tests and an update to the readme.