-
Notifications
You must be signed in to change notification settings - Fork 140
Description
Type of issue
Missing information
Feedback
Consider adding this scenario clarification for customers:
Lets say I started to upgrade my cluster AKS node image to ubuntu20250805 version but the duration window I specified was too short, only 1 nodepool got updated to ubuntu20250805 and 2 additional nodepools were pending to be upgraded. The next time the upgrade triggers , the version that was being processed ubuntu20250805 its pending to be applied to 2 nodepools, but there is a newer image that got released lets say version ubuntu20250820 . What is going to happen with the pending nodepools, will the upgrade process apply the ubuntu20250805 first to the pending nodepools, and later start processing the 3 nopdepools with the newer image ubuntu20250820 if the duration time allows for it?
info:
If a node pool upgrade was interrupted due to time constraints, AKS will resume the upgrade with the previously selected image version (ubuntu20250805) during the next maintenance window
AKS does not automatically override a pending upgrade with a newer image.
Page URL
https://learn.microsoft.com/en-us/azure/aks/planned-maintenance?tabs=azure-cli
Content source URL
https://github.com/MicrosoftDocs/azure-aks-docs/blob/main/articles/aks/planned-maintenance.md
Author
Document Id
880da085-1b0a-6475-8c88-19131e5eee2a
Platform Id
4c8669f2-c6c1-5dd4-2de4-86895dd8b633