Skip to content

Commit afc621d

Browse files
committed
Merge branch 'patch-71' of https://github.com/abhilashaagarwala/azure-stack-docs-pr into aa-contribkubver
2 parents 9051449 + 5d0f871 commit afc621d

File tree

5 files changed

+152
-56
lines changed

5 files changed

+152
-56
lines changed

AKS-Hybrid/TOC.yml

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@
114114
href: cluster-upgrade.md
115115
- name: Create Windows Server containers
116116
href: aks-create-containers.md
117-
- name: Integrate Azure Container Registry with a Kubernetes cluster
117+
- name: Integrate Azure Container Registry
118118
href: deploy-container-registry.md
119119
- name: Monitoring and logging
120120
items:
@@ -134,22 +134,20 @@
134134
href: get-on-demand-logs.md
135135
- name: Troubleshooting
136136
items:
137-
- name: Known issues
138-
href: aks-known-issues.md
139-
- name: Troubleshoot
137+
- name: Troubleshoot & known issues
140138
href: aks-troubleshoot.md
139+
- name: K8sVersionValidation error
140+
href: cluster-k8s-version.md
141141
- name: Use diagnostic checker
142142
href: aks-arc-diagnostic-checker.md
143143
- name: KubeAPIServer unreachable error
144144
href: kube-api-server-unreachable.md
145-
- name: No K8s versions or VM sizes listed for cluster creation
146-
href: cluster-k8s-version.md
147-
- name: Deleted cluster still visible in portal
145+
- name: Cannot see VM SKUs on Azure portal
146+
href: tsg-check-vm-sku.md
147+
- name: Deleted AKS Arc cluster still visible on Azure portal
148148
href: deleted-cluster-visible.md
149149
- name: Can't fully delete AKS Arc cluster with PodDisruptionBudget (PDB) resources
150150
href: delete-cluster-pdb.md
151-
- name: Kubernetes version x.x.x is not available
152-
href: webhook-denied-request.md
153151
- name: Reference
154152
items:
155153
- name: Azure CLI

AKS-Hybrid/aks-troubleshoot.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This article describes how to find solutions for issues you encounter when using
1616

1717
## Open a support request
1818

19-
See the [Get support](/azure/aks/hybrid/help-support?tabs=aksee) article for information about how to use the Azure portal to get support or open a support request for AKS Edge Essentials.
19+
See the [get support](/azure/aks/hybrid/help-support?tabs=aksee) article for information about how to use the Azure portal to get support or open a support request for AKS Arc.
2020

2121
## Upgrade
2222

@@ -28,5 +28,5 @@ If you continually see an [Azure Advisor](/azure/advisor/) upgrade recommendatio
2828
- If you use any of the Azure SDKs, ensure that you are using the latest version of that SDK. You can find the Azure SDKs by searching for "HybridContainerService" on the [Azure SDK releases](https://azure.github.io/azure-sdk/) page.
2929

3030
## Next steps
31-
32-
- [AKS enabled by Azure Arc known issues](aks-known-issues.md)
31+
- [Troubleshoot K8sVersionValidation error](cluster-k8s-version.md)
32+
- [Use diagnostic checker](aks-arc-diagnostic-checker.md)

AKS-Hybrid/cluster-k8s-version.md

Lines changed: 73 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,96 @@
11
---
2-
title: Troubleshoot no K8s versions or VM sizes listed when you create an AKS Arc cluster
3-
description: Learn how to troubleshoot no K8s versions or VM sizes listed when you create an AKS Arc cluster.
2+
title: Troubleshoot K8sVersionValidation error code
3+
description: Learn how to troubleshoot troubleshoot K8sVersionValidation error code
44
ms.topic: troubleshooting
55
author: sethmanheim
66
ms.author: sethm
77
ms.date: 10/02/2024
8-
ms.reviewer: sumsmith
8+
ms.reviewer: abha
99

1010
---
1111

12-
# Troubleshoot no K8s versions or VM sizes listed when you create an AKS Arc cluster
12+
# Troubleshoot K8sVersionValidation error code
1313

14-
The **kubernetesVersions/default** or the **skus/default** resource in Azure is not yet created, or was deleted for some reason. This scenario can happen in older releases when the default resource was not created as a part of the deployment.
14+
This article discusses how to identify and resolve the K8sVersionValidation error code that occurs when you try to create and deploy an AKS cluster on Azure Local.
1515

16-
## Workaround
16+
## Symptoms
1717

18-
Run the following command:
18+
When you try to create an AKS Arc cluster, you receive one of the following error message(s):
19+
20+
> "Kubernetes version 1.27.7 is not ready for use on Linux. Please go to https://aka.ms/aksarccheckk8sversions for details of how to check the readiness of Kubernetes versions"
21+
22+
OR
23+
24+
> Kubernetes version 1.26.12 is not supported. Please go to https://aka.ms/aksarcsupportedversions for details about the supported Kubernetes version on this platform.
25+
26+
OR
27+
28+
> Admission webhook \'vhybridakscluster.kb.io\' denied the request: Kubernetes version 1.26.12 is not available"
29+
30+
31+
## Error messages
32+
33+
### Kubernetes version 1.27.7 is not ready for use on Linux. Please go to https://aka.ms/aksarccheckk8sversions for details of how to check the readiness of Kubernetes versions
34+
35+
#### Linux VHD download has not completed
36+
37+
When you install Azure Local, you download a Linux VHD of approximately 4-5GB in size. This Linux VHD is used to create the underlying VMs for the Kubernetes nodes in your AKS Arc cluster. One cause of the error message is if your Linux VHD has not finished downloading. To resolve this issue, you should wait sometime based on how long it takes for your internet connection to finish downloading the Linux VHD image.
38+
39+
To check if the image download is in progress or has finished, run the below command:
40+
41+
```azurecli
42+
$cl_id = "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.ExtendedLocation/customLocations/<custom_location_name>"
43+
44+
# Get the kubernetes version using CLI (it automatically creates the **kubernetesVersions/default** Azure resource).
45+
46+
az aksarc get-versions --custom-location $cl_id
47+
```
48+
49+
If the above command says that the K8s versions are ready, and you're running Azure Local, [release 2411](/azure/aks/hybrid/aks-whats-new-23h2#release-2411) or newer, file a [support request](help-support.md).
50+
51+
If you're running Azure Local, release 2408 or older, proceed to the below section. **We highly recommend you upgrade your Azure Local deployment to the latest version to get the latest bug fixes and security updates.**
52+
53+
#### Recreate **kubernetesVersions/default**
54+
55+
If you redeploy Azure Local with the same name and parameters, you may have to recreate the **kubernetesVersions/default**. You can run the following commands to do so:
56+
57+
```azurecli
58+
$subscription = <subscription_id>
59+
$cl_id = <custom_location_id>
60+
61+
az login --use-device-code
62+
az account set -s $subscription
63+
$token = $(az account get-access-token --query accessToken)
64+
$url = "https://management.azure.com${cl_id}/providers/Microsoft.HybridContainerService/kubernetesVersions/default?api-version=2024-01-01"
65+
66+
# Get the Kubernetes version Azure resource
67+
az rest --headers "Authorization=Bearer $token" "Content-Type=application/json;charset=utf-8" --uri $url --method GET
68+
69+
# Delete the Kubernetes version Azure resource
70+
az rest --headers "Authorization=Bearer $token" "Content-Type=application/json;charset=utf-8" --uri $url --method DELETE
71+
72+
# Get the Kubernetes version using CLI (it automatically creates the Kubernetes version Azure resource)
73+
az aksarc get-versions --custom-location $cl_id
74+
```
75+
76+
#### I cannot see the Kubernetes versions or VM size options on the Azure portal
77+
78+
This scenario can happen in Azure Local releases 2408 or older, when the default resource for Kubernetes version (or VM sizes) was not created as a part of the Azure Local deployment.
79+
80+
To resolve this issue, run the following command:
1981

2082
```azurecli
2183
$cl_id = "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.ExtendedLocation/customLocations/<custom_location_name>"
2284
23-
# Get the kubernetes version or the VM sizes using CLI (it automatically creates the **kubernetesVersions/default** or the **skus/default** azure resource).
85+
# Get the kubernetes version using CLI (it automatically creates the **kubernetesVersions/default** Azure resource).
2486
2587
az aksarc get-versions --custom-location $cl_id
26-
az aksarc vmsize list --custom-location $cl_id
2788
```
2889

29-
## Validation
90+
### Kubernetes version 1.26.12 is not supported. Please go to https://aka.ms/aksarcsupportedversions for details about the supported Kubernetes version on this platform.
3091

31-
Verify that the portal displays the correct list of supported K8s versions and VM sizes. See [this list of supported K8s versions](aks-whats-new-23h2.md#release-2408) for each Azure Local release.
92+
Azure Local supports specific Kubernetes versions in each of its releases. As stated in the error message, navigate to https://aka.ms/aksarcsupportedversions for list of supported Kubernetes versions based on your deployed Azure Local release.
3293

3394
## Next steps
3495

35-
[Known issues in AKS enabled by Azure Arc](aks-known-issues.md)
96+
[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)

AKS-Hybrid/supported-kubernetes-versions.md

Lines changed: 35 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,16 @@ ms.date: 05/29/2024
77
author: sethmanheim
88
ms.author: sethm
99
ms.lastreviewed: 1/14/2022
10-
ms.reviewer: mikek
10+
ms.reviewer: abha
1111

1212
# Intent: As an IT Pro, I want to know how Kubernetes versions are supported, as well as the lifecycle of clusters in AKS enabled by Azure Arc.
1313
# Keyword: supported Kubernetes versions
1414

1515
---
1616

17-
# Supported Kubernetes versions in AKS
17+
# Supported Kubernetes versions in AKS Arc
1818

19-
This article describes the supported Kubernetes versions for Azure Kubernetes Service enabled by Azure Arc. The Kubernetes community releases minor versions roughly every three months. Recently, the Kubernetes community [increased the support window for each version from nine months to 12 months](https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/), starting with version 1.19.
20-
21-
Minor version releases include new features and improvements. Patch releases are more frequent (sometimes weekly) and are intended for critical bug fixes within a minor version. Patch releases include fixes for security vulnerabilities or major bugs.
19+
This article describes the supported Kubernetes versions for Azure Kubernetes Service enabled by Azure Arc. AKS Arc releases new Kubernetes minor versions roughly every three months.
2220

2321
## Kubernetes versions
2422

@@ -28,8 +26,8 @@ Kubernetes uses the standard [Semantic Versioning](https://semver.org/) versioni
2826
[major].[minor].[patch]
2927
3028
Example:
31-
1.17.7
32-
1.17.8
29+
1.29.2
30+
1.29.5
3331
```
3432

3533
Each number in the version indicates general compatibility with the previous version:
@@ -38,14 +36,27 @@ Each number in the version indicates general compatibility with the previous ver
3836
* **Minor versions** change when functionality updates are made that are backwards compatible to the other minor releases.
3937
* **Patch versions** change when backwards-compatible bug fixes are made.
4038

41-
You should install the latest patch release of the minor version you're running. For example, if your production cluster is on **`1.17.7`**. **`1.17.8`** is the latest available patch version available for the *1.17* series. You should upgrade to **`1.17.8`** as soon as possible to ensure your cluster is fully patched and supported.
39+
You should install the latest patch release of the minor version you're running. For example, if your production cluster is on **`1.29.2`**. **`1.29.5`** is the latest available patch version available for the *1.29* series. You should upgrade to **`1.29.5`** as soon as possible to ensure your Kubernetes cluster is fully patched and supported.
40+
41+
## AKS Arc Kubernetes release calendar
42+
43+
View the current supported Kubernetes version releases on AKS Arc.
44+
45+
| K8s version | Supported Azure Local versions | Current status | Last release with Kubernetes patch/CVE updates |
46+
|--------------|-------------------|--------------|------------|
47+
| 1.30 | TBD | Upcoming | TBD |
48+
| 1.29 | [2411](aks-whats-new-23h2.md#features-and-improvements), [2408](aks-whats-new-23h2.md#release-2408) | Generally available | TBD |
49+
| 1.28 | [2411](aks-whats-new-23h2.md#features-and-improvements), [2408](aks-whats-new-23h2.md#release-2408), [2405](aks-whats-new-23h2.md#release-2405) | Generally available | TBD |
50+
| 1.27 | [2411](aks-whats-new-23h2.md#features-and-improvements), [2408](aks-whats-new-23h2.md#release-2408), [2405](aks-whats-new-23h2.md#release-2405), 2402 | Generally available | 2502 release |
51+
| 1.26 | [2405](aks-whats-new-23h2.md#release-2405), 2402 and older | No more patch versions/CVE updates | 2405 release |
52+
4253

4354
## Kubernetes version support policy
4455

4556
AKS defines a generally available (GA) version as a version that's available for download when deploying or updating AKS enabled by Arc. AKS supports three GA minor versions of Kubernetes:
4657

4758
* The latest GA minor version that is released for AKS (which we refer to as N).
48-
* Two previous minor versions. Each supported minor version also supports a maximum of two (2) stable patches.
59+
* Two previous minor versions. Each supported minor version also supports stable patches.
4960

5061
AKS might also support preview versions, which are explicitly labeled as such.
5162

@@ -54,24 +65,19 @@ AKS might also support preview versions, which are explicitly labeled as such.
5465
5566
The supported window of Kubernetes versions on AKS is known as "N-2": (N (Latest release) - 2 (minor versions)).
5667

57-
For example, if AKS introduces **1.17.a** today, support is provided for the following versions:
68+
For example, if AKS introduces **1.30** today, support is provided for the following versions:
5869

5970
New minor version | Supported Version List
6071
----------------- | ----------------------
61-
1.17.a | 1.17.a, 1.17.b, 1.16.c, 1.16.d, 1.15.e, 1.15.f
62-
63-
Where ".letter" is representative of patch versions.
72+
1.30 | 1.30, 1.29, 1.28
6473

6574
When a new minor version is introduced, the oldest minor version and patch releases supported are deprecated and removed. For example, the current supported version list is:
6675

67-
* 1.17.a
68-
* 1.17.b
69-
* 1.16.c
70-
* 1.16.d
71-
* 1.15.e
72-
* 1.15.f
76+
* 1.29
77+
* 1.28
78+
* 1.27
7379

74-
When AKS releases 1.18.\*, all the 1.15.\* versions are removed and go out of support in 30 days.
80+
When AKS releases 1.30.\*, all the 1.27.\* versions are removed and go out of support in 30 days.
7581

7682
> [!NOTE]
7783
> If you're running an unsupported Kubernetes version, you are asked to upgrade when requesting support for the cluster. Clusters running unsupported Kubernetes releases are not covered by the [AKS support policies](./support-policies.md).
@@ -81,24 +87,23 @@ In addition to this policy, AKS supports a maximum of two patch releases of a gi
8187
```output
8288
Current Supported Version List
8389
------------------------------
84-
1.17.8, 1.17.7, 1.16.10, 1.16.9
90+
1.29.8, 1.29.7, 1.28.10, 1.28.9
8591
```
8692

87-
If AKS releases 1.17.9 and 1.16.11, the oldest patch versions are deprecated and removed, and the supported version list becomes:
93+
If AKS releases 1.29.9 and 1.28.11, the oldest patch versions are deprecated and removed, and the supported version list becomes:
8894

8995
```output
9096
New Supported Version List
9197
----------------------
92-
1.17.*9*, 1.17.*8*, 1.16.*11*, 1.16.*10*
98+
1.29.*9*, 1.29.*8*, 1.28.*11*, 1.28.*10*
9399
```
94100

95101
### Supported `kubectl` versions
96102

97103
You can use one minor version older or newer of `kubectl` relative to your **kube-apiserver** version, consistent with the [Kubernetes support policy for kubectl](https://kubernetes.io/docs/setup/release/version-skew-policy/#kubectl).
98104

99105
For example, if your **kube-apiserver** is at 1.17, then you can use versions 1.16 to 1.18 of `kubectl` with that **kube-apiserver**.
100-
101-
To install or update your version of `kubectl`, run `az AKS on Azure Local and Windows Server install-cli`.
106+
To install or update your version of `kubectl`, run `az aks install-cli`.
102107

103108
## Release and deprecation process
104109

@@ -123,20 +128,18 @@ Specific patch releases may be skipped or rollout accelerated, depending on the
123128

124129
### How does Microsoft notify me of new Kubernetes versions?
125130

126-
The AKS team publishes pre-announcements with planned dates of new Kubernetes versions in our documentation on [GitHub](https://github.com/Azure/aksArc/releases).
131+
The AKS team publishes pre-announcements with planned dates of new Kubernetes versions in AKS Arc documentation.
127132

128133
### How often should I expect to upgrade Kubernetes versions to stay in support?
129134

130135
Starting with Kubernetes 1.19, the [open source community expanded support to one year](https://kubernetes.io/blog/2020/08/31/kubernetes-1-19-feature-one-year-support/). AKS commits to enabling patches and support matching the upstream commitments. For Kubernetes clusters on 1.19 and greater, you'll be able to upgrade a minimum of once a year to stay on a supported version.
131136

132-
For versions on 1.18 or below, the window of support remains at 9 months, requiring an upgrade once every 9 months to stay on a supported version. Regularly test new versions and be prepared to upgrade to newer versions to capture the latest stable enhancements within Kubernetes.
133-
134137
### What happens when a user upgrades a Kubernetes cluster with a minor version that isn't supported?
135138

136139
If you're on the n-3 version or older, it means you're outside of support and are asked to upgrade. When your upgrade from version n-3 to n-2 succeeds, you're back within our support policies. For example:
137140

138-
* If the oldest supported Kubernetes version is 1.15.a and you are on 1.14.b or older, you're outside of support.
139-
* When you successfully upgrade from 1.14.b to 1.15.a or greater, you're back within our support policies.
141+
* If the oldest supported Kubernetes version is 1.27 and you are on 1.26 or older, you're outside of support.
142+
* When you successfully upgrade from 1.26 to 1.27 or greater, you're back within our support policies.
140143

141144
Downgrades are not supported.
142145

@@ -174,8 +177,8 @@ No. Once a version is deprecated/removed, you cannot create a cluster with that
174177

175178
### I am on a freshly deprecated version. Can I still add new node pools? Or do I have to upgrade?
176179

177-
No. You can't add node pools of the deprecated version to your cluster. You can add node pools of a new version. However, this might require you to update the control plane first.
180+
No. You can't add node pools of the deprecated version to your cluster.
178181

179182
## Next steps
180183

181-
For information about how to upgrade your cluster, see [Update the Kubernetes version of AKS clusters](./upgrade.md).
184+
For information about how to upgrade your cluster, see [Update the Kubernetes version of AKS clusters](./cluster-upgrade.md).

AKS-Hybrid/tsg-check-vm-sku.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: Troubleshoot no VM sizes listed on Azure portal
3+
description: Learn how to troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster
4+
ms.topic: troubleshooting
5+
author: sethmanheim
6+
ms.author: sethm
7+
ms.date: 10/02/2024
8+
ms.reviewer: sumsmith
9+
10+
---
11+
12+
# Troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster
13+
14+
When you try creating an AKS Arc cluster from Azure portal, you see that there are no VM sizes listed. This can happen if **skus/default** resource in Azure is not yet created, or was deleted for some reason. This scenario can happen in Azure Local releases 2408 or older, when the default resource was not created as a part of the Azure Local deployment.
15+
16+
## Workaround
17+
18+
Run the following command:
19+
20+
```azurecli
21+
$cl_id = "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.ExtendedLocation/customLocations/<custom_location_name>"
22+
23+
# Get the VM sizes using CLI (it automatically creates the **skus/default** Azure resource).
24+
25+
az aksarc vmsize list --custom-location $cl_id
26+
```
27+
28+
## Validation
29+
30+
Verify that Azure portal now displays the correct list of VM sizes.
31+
32+
## Next steps
33+
34+
[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)

0 commit comments

Comments
 (0)