-
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
rancher-cloudprovider: Improve node group discovery #5361
rancher-cloudprovider: Improve node group discovery #5361
Conversation
Previsouly the rancher provider tried to parse the node `spec.providerID` to extract the node group name. Instead, we now get the machines by the node name and then use a rancher specific label that should always be on the machine. This should work more reliably for all the different node drivers that rancher supports. Signed-off-by: Cyrill Troxler <[email protected]>
/lgtm Although for changes like this I think it would make more sense to uncomment entries in your OWNERS file, so that rancher-specific changes can be reviewed & approved by the people listed there. |
Agreed, but aren't OWNERS required to be members of the Kubernetes org? If so, I guess I'm looking for 2 sponsors ;) |
/assign @towca |
Ah, good point. I guess after reviewing this PR I could qualify as one. You'd still need someone else, from another company. |
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ctrox, mwielgus 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 |
Which component this PR applies to?
cluster-autoscaler
What type of PR is this?
/kind bug
What this PR does / why we need it:
Previsouly the rancher provider tried to parse the node
spec.providerID
to extract the node group name. Instead, we now get the machines by the node name and then use a rancher specific label that should always be on the machine. This should work more reliably for all the different node drivers that rancher supports.Which issue(s) this PR fixes:
Fixes #5140
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: