Skip to content

Conversation

@dghubble
Copy link
Member

  • Set a rolling upgrade policy so that changes to the worker node pool are rolled out gradually. Previously, the VMSS model could change, but instances would not receive it until manually replaced
  • Align Azure node pool behaviors more closely with AWS and GCP:
    • On AWS, worker instance template changes trigger an instance refresh
    • On GCP, worker instance template changes roll out via proactive
  • Define Azure automatic instance repair using Application Health Extension probes to 10256 (kube-proxy or Cilium equivalent) to match the strategy used on Google Cloud

* Set a rolling upgrade policy so that changes to the worker node
pool are rolled out gradually. Previously, the VMSS model could
change, but instances would not receive it until manually replaced
* Align Azure node pool behaviors more closely with AWS and GCP:
  * On AWS, worker instance template changes trigger an instance refresh
  * On GCP, worker instance template changes roll out via proactive
* Define Azure automatic instance repair using Application Health
Extension probes to 10256 (kube-proxy or Cilium equivalent) to match
the strategy used on Google Cloud
@dghubble dghubble merged commit f70b37d into main Jun 20, 2025
@dghubble dghubble deleted the azure-upgrade-policy branch June 20, 2025 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants