Skip to content

Commit f682b4c

Browse files
author
amsliu
committed
minor update based on edit review feedback
1 parent 67e464a commit f682b4c

1 file changed

Lines changed: 13 additions & 7 deletions

File tree

support/azure/azure-kubernetes/error-codes/upgradefailed-error.md

Lines changed: 13 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Troubleshoot the UpgradeFailed Error
3-
description: Learn how to troubleshoot the UpgradeFailed error when you try to upgrade an AKS cluster by using the Azure CLI.
4-
ms.date: 08/05/2025
2+
title: Troubleshoot a failed AKS cluster upgrade
3+
description: Learn how to troubleshoot error codes related to upgrade failure when you try to upgrade an AKS cluster by using the Azure CLI.
4+
ms.date: 08/07/2025
55
editor: v-jsitser
66
ms.reviewer: v-liuamson
77
ms.service: azure-kubernetes-service
@@ -43,24 +43,30 @@ To understand more about these errors, see [AKS supported Kubernetes versions](h
4343
## Resolution
4444

4545
To resolve this issue, follow these steps.
46-
46+
4747
**Step 1:** Verify the current version and available upgrade paths. To view the current Kubernetes version and supported upgrade targets, run the following command:
4848

49-
> az aks get-upgrades \--resource-group \<RG\> \--name \<ClusterName\> \--output table
49+
```azurecli
50+
az aks get-upgrades --resource-group <RG> --name <ClusterName> --output table
51+
```
5052

5153
If only newer versions, such as 1.29.*x*, are listed, and intermediate versions, such as 1.27.*x*, 1.26.*x*, or 1.25.*x*, are missing, the missing versions are deprecated in your region.
5254

5355
**Step 2:** Try to run a full upgrade (control plane and node pool together). Because of the version skew policy (control planes can't be more than three minor versions ahead of node pools), a separate control plane-only upgrade might fail. Instead, upgrade both the control plane and node pool together:
5456

55-
> az aks upgrade \--resource-group \<RG\> \--name \<ClusterName\> \--kubernetes-version \<available upgrade version\> \--yes
57+
```azurecli
58+
az aks upgrade \--resource-group \<RG\> \--name \<ClusterName\> \--kubernetes-version \<available upgrade version\> \--yes
59+
```
5660

5761
This action ensures compliance with the version skew policy by coordinating a supported Kubernetes version and an upgrade of both components.
5862

5963
## More information
6064

6165
- Always verify the supported versions in your region by running the following command:
6266

63-
> az aks get-versions \--location \<region\> \--output table
67+
```azurecli
68+
az aks get-versions \--location \<region\> \--output table
69+
```
6470

6571
- Avoid trying to upgrade to deprecated versions. AKS might enforce immediate skips of supported long-term versions (for example, 1.29).
6672

0 commit comments

Comments
 (0)