Skip to content

Commit 79b040b

Browse files
sethmanheimsethmanheim
authored
Merge pull request #15964 from sethmanheim/aks-tsg
Add new AKS known issues
2 parents 0c4bc39 + f174ba2 commit 79b040b

File tree

5 files changed

+148
-2
lines changed

5 files changed

+148
-2
lines changed

‎AKS-Hybrid/TOC.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -134,6 +134,12 @@
134134
href: aks-arc-diagnostic-checker.md
135135
- name: KubeAPIServer unreachable error
136136
href: kube-api-server-unreachable.md
137+
- name: No K8s versions or VM sizes listed for cluster creation
138+
href: cluster-k8s-version.md
139+
- name: Deleted cluster still visible in portal
140+
href: deleted-cluster-visible.md
141+
- name: Kubernetes version x.x.x is not available
142+
href: webhook-denied-request.md
137143
- name: Reference
138144
items:
139145
- name: Azure CLI

‎AKS-Hybrid/cluster-k8s-version.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
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.
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 K8s versions or VM sizes listed when you create an AKS Arc cluster
13+
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.
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 kubernetes version or the VM sizes using CLI (it automatically creates the **kubernetesVersions/default** or the **skus/default** azure resource).
24+
25+
az aksarc get-versions --custom-location $cl_id
26+
az aksarc vmsize list --custom-location $cl_id
27+
```
28+
29+
## Validation
30+
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 Stack HCI release.
32+
33+
## Next steps
34+
35+
[Known issues in AKS enabled by Azure Arc](aks-known-issues.md)

‎AKS-Hybrid/deleted-cluster-visible.md

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: Troubleshoot deleted cluster still visible in portal
3+
description: Learn how to troubleshoot deleted cluster still visible in portal, shows "Not found."
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+
# Deleted cluster still visible in portal, shows "Not found"
13+
14+
A provisioned cluster that you deleted is still visible in the **Overview** blade on the Azure portal. Selecting the resource shows a **Not found** message. This error happens because occasionally, the cluster delete command fails to fully remove a resource. While it might delete the child **provisionedClusterInstance** resource, the parent **connectedCluster** resource often remains, making it still visible in the portal.
15+
16+
## Verify
17+
18+
- Get the provisioned cluster instance resource and verify that it doesn't exist:
19+
20+
```azurecli
21+
az aksarc show -g <resource_group> -n <cluster_name>
22+
```
23+
24+
- Get the connected cluster resource and verify that it exists:
25+
26+
```azurecli
27+
az connectedk8s show -g <resource_group> -n <cluster_name>
28+
```
29+
30+
## Workaround
31+
32+
Run the following command:
33+
34+
```azurecli
35+
# Replace the following values appropriately
36+
37+
$subscription = <subscription_id>
38+
$resource_group = <resource_group_name>
39+
$cluster_name = <cluster_name>
40+
41+
az aksarc delete -g <resource_group> -n <cluster_name>
42+
```
43+
44+
This command deletes the parent connected cluster resource as well.
45+
46+
## Validation
47+
48+
Run the `az connectedk8s show -g <resource_group> -n <cluster_name>` command to verify that it returns "Not found," or verify that the portal doesn't list the connected cluster resource anymore.
49+
50+
## Next steps
51+
52+
[Known issues in AKS enabled by Azure Arc](aks-known-issues.md)

‎AKS-Hybrid/known-issues-workload-clusters.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -398,8 +398,7 @@ sections:
398398
```powershell
399399
crictl pull ecpacr.azurecr.io/kube-proxy:<Kubernetes version>
400400
```
401-
402-
401+
403402
additionalContent: |
404403
## Next steps
405404
- [Troubleshooting overview](troubleshoot-overview.md)

‎AKS-Hybrid/webhook-denied-request.md

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Troubleshoot admission webhook denied the request - Kubernetes version x.x.x is not available
3+
description: Learn how to troubleshoot admission webhook denied the request - Kubernetes version x.x.x is not available.
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+
# Admission webhook 'vhybridakscluster.kb.io' denied the request: Kubernetes version x.x.x is not available
13+
14+
When you create an AKS Arc cluster from the Azure portal or using CLI, the following error is returned:
15+
16+
```output
17+
{
18+
"code": "BadRequest",
19+
"message": "admission webhook \'vhybridakscluster.kb.io\' denied the request: Kubernetes version x.x.x is not available"
20+
}
21+
```
22+
23+
## Workaround
24+
25+
Run the following commands:
26+
27+
```azurecli
28+
$subscription = <subscription_id>
29+
$cl_id = <custom_location_id>
30+
31+
az login --use-device-code
32+
az account set -s $subscription
33+
$token = $(az account get-access-token --query accessToken)
34+
$url = "https://management.azure.com${cl_id}/providers/Microsoft.HybridContainerService/kubernetesVersions/default?api-version=2024-01-01"
35+
36+
# Get the Kubernetes version Azure resource
37+
az rest --headers "Authorization=Bearer $token" "Content-Type=application/json;charset=utf-8" --uri $url --method GET
38+
39+
# Delete the Kubernetes version Azure resource
40+
az rest --headers "Authorization=Bearer $token" "Content-Type=application/json;charset=utf-8" --uri $url --method DELETE
41+
42+
# Get the Kubernetes version using CLI (it automatically creates the Kubernetes version Azure resource)
43+
az aksarc get-versions --custom-location $cl_id
44+
```
45+
46+
## Validation
47+
48+
Verify that the `az aksarc get-versions --custom-location <custom_location_id>` command, or the portal, returns the corrected list of supported K8s versions, and that the error "admission webhook \'vhybridakscluster.kb.io\' denied the request: Kubernetes version x.x.x is not available" does not recur when you recreate the cluster with the correct K8s version.
49+
50+
Make sure you validate the K8s version against the [supported K8s versions](aks-whats-new-23h2.md#release-2408).
51+
52+
## Next steps
53+
54+
[Known issues in AKS enabled by Azure Arc](aks-known-issues.md)

0 commit comments

Comments
 (0)