azure: detect VMs needing update from latestModelApplied - #18669
Conversation
|
/test pull-kops-azure-upgrade-dns-none |
|
@hakman: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
CCM owns cloud-node-lifecycle, which deletes the Node objects of deleted VMs. A single replica can be scheduled onto the node a rolling update is about to replace, leaving nothing to delete the stale Node object once that VM is gone. Its orphaned pods then keep the cluster from validating. Stay at one replica without an HA control plane, because the pods are hostNetwork and would otherwise fight over the secure port.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cc @rifelpet @ameukam