Commits on May 18, 2020

1. Azure: support non-VMSS instances removal …

   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

   

   bpineau authored and andyzhangx committed May 18, 2020
   Copy the full SHA

   89fe5cb View commit details

   Browse the repository at this point in the history