-
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
CAPI: Do not normalize Node IDs outside of CAPI provider #3057
Conversation
/assign @hardikdr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice find Joel!
/lgtm
Referencing the particular commit which normalized to be able to match nodes/machines d9e3197 However that ^^ only partially fixed the problem. This will still break for some scenarios e.g upstream cluster-api-provider-aws as its providerID does not includes the AZ consistently with the control manager cloud provider. We should probably fix there as well -> https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/22be31dd76da04409c425c77e2967db327f409a4/controllers/awsmachine_controller.go#L406 |
/hold Need to make sure this doesn't merge until @enxebre's comment is resolved |
c76fb8d
to
5e0126a
Compare
This will need resolving before this PR can be unblocked kubernetes-sigs/cluster-api-provider-aws#1693 |
That second change finished the trick: my autoscaled nodes now persist for as long as load does, rather than rolling every 10 minutes. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enxebre 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 |
/lgtm |
/hold cancel |
[CA-1.18] #3057 cherry-pick: CAPI: Do not normalize Node IDs outside of CAPI provider
When #1866 introduced the CAPI provider, all Provider IDs from nodes were being normalized so that internally, there were no differences (eg some places using normalized, some not)
However, the clusterstateregistry and anything outside of the CPAI provider does not expect the instance IDs to be normalized, and so nodes were being marked as unregistered due to the normalized ID not matching the non-normalized ID coming from the Nodes on the cluster.
This PR makes it so that Instance IDs fetched and passed externally are not normalized, fixing the unregistered node logic in the clusterstateregistry when using the CAPI provider.
/cc @enxebre @elmiko