Sync release-aks-ee-feb with main

Sync release-aks-ee-feb with main

Author: sethmanheim

.openpublishing.redirection.aks.json

@@ -144,20 +144,28 @@
             href: kubernetes-monitor-metrics.md
   - name: Troubleshooting
     items:
-    - name: Troubleshoot & known issues
+    - name: Troubleshoot and known issues
       href: aks-troubleshoot.md
+    - name: Control plane configuration validation errors
+      href: control-plane-validation-errors.md
+    - name: Connectivity issues with MetalLB
+      href: load-balancer-issues.md 
     - name: K8sVersionValidation error
       href: cluster-k8s-version.md
     - name: Use diagnostic checker
       href: aks-arc-diagnostic-checker.md
     - name: KubeAPIServer unreachable error
       href: kube-api-server-unreachable.md
     - name: Can't see VM SKUs on Azure portal
-      href: tsg-check-vm-sku.md
+      href: check-vm-sku.md
     - name: Deleted AKS Arc cluster still visible on Azure portal
       href: deleted-cluster-visible.md
     - name: Can't fully delete AKS Arc cluster with PodDisruptionBudget (PDB) resources
       href: delete-cluster-pdb.md
+    - name: Azure Advisor upgrade recommendation
+      href: azure-advisor-upgrade.md
+    - name: Issues after deleting storage volumes
+      href: delete-storage-volume.md
   - name: Reference
     items:
     - name: Azure CLI

AKS-Arc/TOC.yml

@@ -3,7 +3,7 @@ title: Troubleshoot common issues in AKS enabled by Azure Arc
 description: Learn about common issues and workarounds in AKS enabled by Arc.
 ms.topic: how-to
 author: sethmanheim
-ms.date: 11/22/2024
+ms.date: 02/28/2025
 ms.author: sethm 
 ms.lastreviewed: 02/27/2024
 ms.reviewer: guanghu
@@ -12,22 +12,27 @@ ms.reviewer: guanghu
 
 # Troubleshoot common issues in AKS enabled by Azure Arc
 
-This article describes how to find solutions for issues you encounter when using AKS enabled by Azure Arc. Known issues and errors are organized by functional area. You can use the links provided in this article to find solutions and workarounds to resolve them.
+This section describes how to find solutions for issues you encounter when using AKS enabled by Azure Arc.
 
 ## Open a support request
 
-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.
+To open a support request, see the [Get support](/azure/aks/hybrid/help-support) article for information about how to use the Azure portal to get support or open a support request for AKS Arc.
 
-## Upgrade
+## Known issues
 
-### Azure Advisor upgrade recommendation
+The following sections describe known issues and workarounds for AKS enabled by Azure Arc:
 
-If you continually see an [Azure Advisor](/azure/advisor/) upgrade recommendation that says "Upgrade to the latest version of AKS enabled by Azure Arc," follow these steps to disable the recommendation:
-
-- Ensure that you update your Azure Local solution to the latest version. For more information, see [About updates for Azure Local, version 23H2](/azure-stack/hci/update/about-updates-23h2).
-- If you use any of the Azure SDKs, ensure that you're 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.
+- [Control plane configuration validation errors](control-plane-validation-errors.md)
+- [Connectivity issues with MetalLB](load-balancer-issues.md)
+- [K8sVersionValidation error](cluster-k8s-version.md)
+- [Use diagnostic checker](aks-arc-diagnostic-checker.md)
+- [KubeAPIServer unreachable error](kube-api-server-unreachable.md)
+- [Can't see VM SKUs on Azure portal](check-vm-sku.md)
+- [Deleted AKS Arc cluster still visible on Azure portal](deleted-cluster-visible.md)
+- [Can't fully delete AKS Arc cluster with PodDisruptionBudget (PDB) resources](delete-cluster-pdb.md)
+- [Azure Advisor upgrade recommendation message](azure-advisor-upgrade.md)
+- [Issues after deleting storage volume](delete-storage-volume.md)
 
 ## Next steps
 
-- [Troubleshoot K8sVersionValidation error](cluster-k8s-version.md)
-- [Use diagnostic checker](aks-arc-diagnostic-checker.md)
+[What is AKS enabled by Azure Arc?](aks-overview.md)

AKS-Arc/aks-troubleshoot.md

@@ -0,0 +1,28 @@
+---
+title: Azure Advisor upgrade recommendation
+description: Learn how to disable Azure Advisor upgrade recommendation alerts.
+author: sethmanheim
+ms.author: sethm
+ms.topic: troubleshooting
+ms.date: 02/28/2025
+
+---
+
+# Azure Advisor upgrade recommendation
+
+This article describes how to disable recurring Azure Advisor upgrade recommendation alerts for AKS enabled by Azure Arc.
+
+## Symptoms
+
+You continually see an Azure Advisor upgrade recommendation that says **Upgrade to the latest version of AKS enabled by Azure Arc**.
+
+## Workaround
+
+Follow these steps to disable the recommendation:
+
+- Ensure that you update your Azure Local solution to the latest version. For more information, see [About updates for Azure Local, version 23H2](/azure-stack/hci/update/about-updates-23h2).
+- If you use any of the Azure SDKs, ensure that you're 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.
+
+## Next steps
+
+[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)

AKS-Arc/azure-advisor-upgrade.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot no VM sizes listed on Azure portal
-description: Learn how to troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster
+description: Learn how to troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster.
 ms.topic: troubleshooting
 author: sethmanheim
 ms.author: sethm
@@ -9,7 +9,7 @@ ms.reviewer: sumsmith
 
 ---
 
-# Troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster
+# No VM sizes listed on Azure portal when you create an AKS Arc cluster
 
 When you try to create an AKS Arc cluster from the Azure portal, you can see that there are no VM sizes listed. This can happen if the **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.
 

AKS-Arc/tsg-check-vm-sku.md renamed to AKS-Arc/check-vm-sku.md

@@ -1,7 +1,7 @@
 ---
 title: Configure SSH keys for a cluster in AKS enabled by Azure Arc
 description: Learn how to configure SSH keys for an AKS Arc cluster.
-ms.date: 01/10/2025
+ms.date: 02/26/2025
 ms.topic: how-to
 author: sethmanheim
 ms.author: sethm
@@ -71,16 +71,9 @@ You have three options for SSH key configuration:
 - Use an existing key stored in Azure and select from the stored keys.
 - Use an existing public key by providing the SSH public key value.
 
-## Error message
+## Error messages
 
-If you don't provide valid SSH key information during cluster creation and no SSH key exists, you receive error messages like the following:
-
-- An RSA key file or key value must be supplied to SSH Key Value.
-- Control Plane: Missing Security Keys in Cluster Configuration.
-- LinuxProfile SSH public keys should be valid and non-empty.
-- Global LinuxProfile SSH public keys should be valid and non-empty.
-
-To mitigate the issue, see [Create and manage SSH keys with the Azure CLI](/azure/virtual-machines/ssh-keys-azure-cli#generate-new-keys) to create the SSH keys. Then, see [Create Kubernetes clusters](aks-create-clusters-cli.md) for the interface you're using. If you're using the REST API, see [provisioned cluster instances](/rest/api/hybridcontainer/provisioned-cluster-instances) to create the provisioned cluster instance.
+For information about error messages that can occur when you create and deploy an AKS cluster on Azure Local, see the [Control plane configuration validation errors](control-plane-validation-errors.md) article.
 
 ## Next steps
 

AKS-Arc/configure-ssh-keys.md

@@ -0,0 +1,53 @@
+---
+title: Control plane configuration validation errors
+description: Learn details about each control plane configuration validation error.
+author: sethmanheim
+ms.author: sethm
+ms.topic: troubleshooting
+ms.date: 02/26/2025
+
+---
+
+# Control plane configuration validation errors
+
+This article describes how to identify and resolve [ControlPlaneConfigurationValidation](configure-ssh-keys.md) error codes that can occur when you create and deploy an AKS cluster on Azure Local.
+
+## Symptoms
+
+When you try to create an AKS Arc cluster, you receive an error message that appears as follows:
+
+```json
+admission webhook "vhybridakscluster.kb.io" denied the request: { 
+   "result": "Failed", 
+   "validationChecks": [ 
+      { 
+         "name": "ControlPlaneConfigurationValidation", 
+         "message": "ControlPlane: Global LinuxProfile SSH public keys should be valid and non-empty. ssh: no key found", 
+         "recommendation": "Please check https://aka.ms/AKSArcValidationErrors/ControlPlaneConfigurationValidation for recommendations" 
+      } 
+   ] 
+}
+```
+
+The following section describes the error messages that you might see when you encounter the **ControlPlaneConfigurationValidation** error code.
+
+## Global LinuxProfile SSH public keys must be valid and non-empty
+
+If you don't provide valid SSH key information during Kubernetes cluster creation and no SSH key exists, you receive error messages similar to the following:
+
+- An RSA key file or key value must be supplied to SSH Key Value.
+- Control Plane: Missing Security Keys in Cluster Configuration.
+- LinuxProfile SSH public keys should be valid and non-empty.
+- Global LinuxProfile SSH public keys should be valid and non-empty.
+
+To mitigate the issue, see [Generate and store SSH keys with the Azure CLI](/azure/virtual-machines/ssh-keys-azure-cli#generate-new-keys) to create the SSH keys. Then, see [Create Kubernetes clusters](aks-create-clusters-cli.md) for the interface you're using. If you're using the REST API, see [provisioned cluster instances](/rest/api/hybridcontainer/provisioned-cluster-instances) to create the provisioned cluster instance.
+
+## Control plane count and VM size
+
+In Kubernetes, control plane nodes manage and orchestrate the cluster. They run key components such as API Server, etcd, scheduler, etc. Control plane nodes maintain cluster state, schedule workloads, and ensure high availability, often using multiple nodes for redundancy.
+
+To successfully create an AKS Arc cluster, you must specify at least one control plane node count. Also, to maintain etcd quorum, the control plane node count should be an odd number. For more information about supported count and VM SKU options, see [Scale requirements for AKS on Azure Local](scale-requirements.md#support-count-for-aks-on-azure-local).
+
+## Next steps
+
+[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)

AKS-Arc/control-plane-validation-errors.md

@@ -0,0 +1,28 @@
+---
+title: AKS on Azure Local issues after deleting storage volumes
+description: Learn how to mitigate issues after deleting storage volumes.
+author: sethmanheim
+ms.author: sethm
+ms.topic: troubleshooting
+ms.date: 02/28/2025
+
+---
+
+# AKS on Azure Local issues after deleting storage volumes
+
+This article describes how to mitigate cluster issues if a storage volume is deleted.
+
+## Symptoms
+
+AKS Arc workload data is stored on Azure Local storage volumes, including the AKS Arc node disks and persistent volumes of data disks. If the storage volume is accidentally deleted, the AKS Arc cluster doesn't work properly, as its data is removed as well.
+
+## Workaround
+
+To manage storage volumes on Azure Local, follow these steps:
+
+- Ensure that you deleted all the storage path(s) that are created on that storage volume. Deleting storage paths raises an alert to indicate the workload that was stored on it. To delete the storage path, see [Delete a storage path](/azure/azure-local/manage/create-storage-path?view=azloc-24112&preserve-view=true&tabs=azurecli#delete-a-storage-path).
+- If you have an AKS Arc cluster that must be deleted, see [Delete the AKS Arc cluster](aks-create-clusters-cli.md#delete-the-cluster).
+
+## Next steps
+
+[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)

AKS-Arc/delete-storage-volume.md

@@ -55,7 +55,7 @@
       "feedback_product_url": "https://feedback.azure.com/d365community/forum/a2f8da29-b853-ec11-8f8e-0022481f2fe7",
       "breadcrumb_path": "/azure/aks/aksarc/breadcrumb/toc.json",
       "extendBreadcrumb": false,
-      "manager":"femila",
+      "manager":"lizross",
       "ms.service": "azure-stack",
       "recommendations": true,
       "zone_pivot_group_filename": "../azure-stack/zone-pivot-groups.json"

AKS-Arc/docfx.json

@@ -0,0 +1,61 @@
+---
+title: Intermittent connectivity issues with MetalLB or Kubernetes services of type Load Balancer
+description: Learn how to mitigate connection issues with MetalLB or Kubernetes services of type Load Balancer.
+author: sethmanheim
+ms.author: sethm
+ms.topic: troubleshooting
+ms.date: 02/26/2025
+
+---
+
+# Intermittent connectivity issues with MetalLB or Kubernetes services of type Load Balancer
+
+You might sometimes experience intermittent connectivity issues when accessing a Kubernetes service of type **LoadBalancer** using the assigned external IP address. This article describes how to identify and resolve connection issues with MetalLB or Kubernetes services of type **LoadBalancer**.
+
+## Symptoms
+
+- The service is accessible sometimes, but not consistently.
+- The client experiences unexpected disconnects.
+- The external IP intermittently appears and disappears from the control plane when running `Get-VMNetworkAdapter`:
+
+  ```powershell
+  Get-VMNetworkAdapter -VMName * | select name, ipaddresses 
+
+  ...
+
+  # The external IP appears in the get-vmnetworkadapter output 
+
+  nocpip26-55bc418a-control-plane-kjqcm-nic-b607b1e0                         
+  {172.16.0.11, 172.16.0.10, ***172.16.100.0***, fe80::ec:d3ff:fe8b:1} 
+
+  # Now it's gone 
+
+  Get-VMNetworkAdapter -VMName * | select name, ipaddresses 
+
+  ...
+
+  nocpip26-55bc418a-control-plane-kjqcm-nic-b607b1e0                         
+  {172.16.0.11, 172.16.0.10, ***Now it is gone*** fe80::ec:d3ff:fe8b:1} 
+
+  # Now it's back 
+
+  Get-VMNetworkAdapter -VMName * | select name, ipaddresses
+
+  ... 
+
+  nocpip26-55bc418a-control-plane-kjqcm-nic-b607b1e0                         
+  {172.16.0.11, 172.16.0.10, ***172.16.100.0***, fe80::ec:d3ff:fe8b:1}
+  ```
+
+## Mitigation
+
+This issue was fixed in [AKS on Azure Local, version 2411](aks-whats-new-23h2.md#release-2411).
+
+If you're on an older build, please update to Azure Local, version 2411. Once you update to 2411, you can:
+
+- Create a new AKS cluster. The new AKS cluster should not have any intermittent load balancer connectivity issues.
+- [Upgrade the Kubernetes version](cluster-upgrade.md) of your existing AKS cluster to get the fix.
+
+## Next steps
+
+[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)