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 #91184: Azure: support non-VMSS instances removal #91200
Automated cherry pick of #91184: Azure: support non-VMSS instances removal #91200
Conversation
/kind bug |
When called by Controller Manager lifecycle controller for a node missing heartbeats (via `InstanceShutdownByProviderID()`), Azure cloud provider ensures the instance backing that node is shut down or otherwise removed from its containing VMSS before allowing the node to be reaped from the cluster. But it won't test the same for VMAS or standalone instances (not part of a VMSS), which are otherwise well supported: they can register, for instance. So deleted non-VMSS instances will leave `NotReady` nodes behind, and, depending on their name, might cause regular VMSS List / full re-scans. fix build failure
ff9bbaf
to
89fe5cb
Compare
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: andyzhangx, feiskyer 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 |
Cherry pick of #91184 on release-1.17.
#91184: Azure: support non-VMSS instances removal
For details on the cherry pick process, see the cherry pick requests page.