|
1 | 1 | --- |
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 |
5 | 5 | editor: v-jsitser |
6 | 6 | ms.reviewer: v-liuamson |
7 | 7 | ms.service: azure-kubernetes-service |
@@ -43,24 +43,30 @@ To understand more about these errors, see [AKS supported Kubernetes versions](h |
43 | 43 | ## Resolution |
44 | 44 |
|
45 | 45 | To resolve this issue, follow these steps. |
46 | | - |
| 46 | + |
47 | 47 | **Step 1:** Verify the current version and available upgrade paths. To view the current Kubernetes version and supported upgrade targets, run the following command: |
48 | 48 |
|
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 | +``` |
50 | 52 |
|
51 | 53 | 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. |
52 | 54 |
|
53 | 55 | **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: |
54 | 56 |
|
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 | +``` |
56 | 60 |
|
57 | 61 | This action ensures compliance with the version skew policy by coordinating a supported Kubernetes version and an upgrade of both components. |
58 | 62 |
|
59 | 63 | ## More information |
60 | 64 |
|
61 | 65 | - Always verify the supported versions in your region by running the following command: |
62 | 66 |
|
63 | | - > az aks get-versions \--location \<region\> \--output table |
| 67 | +```azurecli |
| 68 | +az aks get-versions \--location \<region\> \--output table |
| 69 | +``` |
64 | 70 |
|
65 | 71 | - Avoid trying to upgrade to deprecated versions. AKS might enforce immediate skips of supported long-term versions (for example, 1.29). |
66 | 72 |
|
|
0 commit comments