This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 19%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
Hi Team,
We had upgrade our aks cluster using below command in CLI:
az aks upgrade --resource-group rg-name --name k8s-cluster --kubernetes-version 1.29.15 --enable-force-upgrade --upgrade-override-until 2025-04-12T10:15:00Z
Even though until 2025-04-12T10:15:00Z flag is mentioned. This parameter has not been deleted till now in azure portal.
Could please tell us what is the reason for this behaviour and how to unset this ?
In the json view, we can still see :
"upgradeSettings": { "overrideSettings": { "forceUpgrade": true, "until": "2025-04-12T10:15:00Z" } }
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 79%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
Hello Nagashree •,
Did you try working with this- https://learn.microsoft.com/en-us/azure/aks/stop-cluster-upgrade-api-breaking-changes?source=recommendations#bypass-validation-to-ignore-api-changes
Note- This method requires you to use the Azure CLI version 2.57 or later. If you have the preview CLI extension installed, you need to update to version 3.0.0b10 or later. This method isn't recommended, as deprecated APIs in the targeted Kubernetes version might not work long term. We recommend removing them as soon as possible after the upgrade completes.
If you have any further queries, do let us know.
Hello Nagashree,
Checking to see whether you have resolved the issue with the solution provided above, or if you need any further assistance, please let us know. We are happy to help.
We have already upgraded our cluster using command:
az aks upgrade --resource-group rg-name --name k8s-cluster --kubernetes-version 1.29.15 --enable-force-upgrade --upgrade-override-until 2025-04-12T10:15:00Z
My question is why we see below block in cluster overview json-view page even though the date has been expired. Why this parameter is not removed from cluster.
"upgrade_override": [{"effective_until": "2025-04-12T10:15:00Z","force_upgrade_enabled": true} ]
we are upgrading our azurerm version and it is telling we can't unset upgrade_override.
Is there command to unset this upgrade override parameter ?
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 12%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVC%3C/text%3E%3C/svg%3E)
Once configured 'upgradeSettings': {
'overrideSettings': {
'forceUpgrade': false,
'until': '2024-08-08T18:26:25.037276+00:00'
}
}, its not possible to unset upgradeSettings.until, public documentation should be updated soon with this note.
Hello Nagashree,
Azure does not automatically remove the upgrade_override block from the cluster metadata. This is expected behavior, as the setting is persistent and remains in place until it is explicitly removed or modified.
To potentially clear the override, you can re-run the upgrade command without the --enable-force-upgrade and --upgrade-override-until flags. This can trigger Azure to clean up the override setting, assuming the upgrade conditions no longer require it.
az aks upgrade \
--resource-group rg-name \
--name k8s-cluster \
--kubernetes-version 1.29.15
Try the above command and if you have any further queries, do let us know.