Acrolinx

Author: sethmanheim

AKS-Hybrid/deleted-cluster-visible.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot deleted cluster still visible in portal
-description: Learn how to troubleshoot deleted cluster still visible in portal, shows "Not found".
+description: Learn how to troubleshoot deleted cluster still visible in portal, shows "Not found."
 ms.topic: troubleshooting
 author: sethmanheim
 ms.author: sethm
@@ -11,11 +11,11 @@ ms.reviewer: sumsmith
 
 # Deleted cluster still visible in portal, shows "Not found"
 
-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 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.
+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.
 
 ## Verify
 
-- Get the provisioned cluster instance resource and verify that it does not exist:
+- Get the provisioned cluster instance resource and verify that it doesn't exist:
 
   ```azurecli
   az aksarc show -g <resource_group> -n <cluster_name>

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

@@ -398,107 +398,6 @@ sections:
             ```powershell
             crictl pull ecpacr.azurecr.io/kube-proxy:<Kubernetes version>
             ```
-      - question: |
-          When you create an AKS Arc cluster from the Azure portal, no K8s versions or VM sizes are listed
-
-        answer: |
-          The **kubernetesVersions/default** or the **skus/default** Azure Resource Manager resource is not yet created, or was deleted for some reason. This scenario can happen in older releases when AKS didn't create the default resource as a part of the deployment in the **ArcHci** module.
-
-          ### Workaround
-
-          Run the following command:
-
-          ```azurecli
-          $cl_id = "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/providers/Microsoft.ExtendedLocation/customLocations/<custom_location_name>"
-          
-          # Get the kubernetes version or the VM sizes using CLI (it automatically creates the **kubernetesVersions/default** or the **skus/default** azure resource).
-
-          az aksarc get-versions --custom-location $cl_id
-          az aksarc vmsize list --custom-location $cl_id
-          ```
-
-          ### Validation
-
-          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.
-      - question: |
-          Deleted cluster still visible in portal, shows "Not found"
-
-        answer: |
-          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 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.
-
-          ### Verify
-
-          - Get the provisioned cluster instance resource and verify that it does not exist:
-
-            ```azurecli
-            az aksarc show -g <resource_group> -n <cluster_name>
-            ```
-
-          - Get the connected cluster resource and verify that it exists:
-
-            ```azurecli
-            az connectedk8s show -g <resource_group> -n <cluster_name>
-            ```
-
-          ### Workaround
-
-          Run the following command:
-
-          ```azurecli
-          # Replace the following values appropriately
-
-          $subscription = <subscription_id>
-          $resource_group = <resource_group_name>
-          $cluster_name = <cluster_name>
-
-          az aksarc delete -g <resource_group> -n <cluster_name>
-          ```
-
-          This command deletes the parent connected cluster resource as well.
-
-          ### Validation
-
-          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.
-
-      - question: |
-          Admission webhook 'vhybridakscluster.kb.io' denied the request: Kubernetes version x.x.x is not available
-
-        answer: |
-          When you create an AKS Arc cluster from the Azure portal or using CLI, the following error is returned:
-
-          ```output
-          {
-            "code": "BadRequest",
-            "message": "admission webhook \'vhybridakscluster.kb.io\' denied the request: Kubernetes version x.x.x is not available"
-          }
-          ```
-
-          ### Workaround
-
-          Run the following command:
-
-          ```azurecli
-          $subscription = <subscription_id>
-          $cl_id = <custom_location_id>
-
-          az login --use-device-code
-          az account set -s $subscription
-          $token = $(az account get-access-token --query accessToken)
-          $url = "https://management.azure.com${cl_id}/providers/Microsoft.HybridContainerService/kubernetesVersions/default?api-version=2024-01-01"
-
-          # Get the Kubernetes version Azure resource
-          az rest --headers "Authorization=Bearer $token" "Content-Type=application/json;charset=utf-8" --uri $url --method GET
-
-          # Delete the Kubernetes version Azure resource
-          az rest --headers "Authorization=Bearer $token" "Content-Type=application/json;charset=utf-8" --uri $url --method DELETE
-
-          # Get the Kubernetes version using CLI (it automatically creates the Kubernetes version Azure resource)
-          az aksarc get-versions --custom-location $cl_id
-          ```
-
-          ### Validation
-
-          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.
 
 additionalContent: |
   ## Next steps