Updates

Author: sethmanheim

AKS-Hybrid/TOC.yml

@@ -142,7 +142,7 @@
       href: aks-arc-diagnostic-checker.md
     - name: KubeAPIServer unreachable error
       href: kube-api-server-unreachable.md
-    - name: Cannot see VM SKUs on Azure portal
+    - name: Can't see VM SKUs on Azure portal
       href: tsg-check-vm-sku.md
     - name: Deleted AKS Arc cluster still visible on Azure portal
       href: deleted-cluster-visible.md

AKS-Hybrid/aks-hci-ip-address-planning.md

@@ -55,6 +55,7 @@ Continuing with this example, and adding it to the following table, you get:
 ### LNETs considerations for AKS clusters and Arc VMs
 
 Logical networks on Azure Local are used by both AKS clusters and Arc VMs. You can configure logical networks in one of the following 2 ways:
+
 - Share a logical network between AKS and Arc VMs.
 - Define separate logical networks for AKS clusters and Arc VMs.
 
@@ -81,7 +82,7 @@ AKS provides a **default value of 10.244.0.0/16** for the pod network CIDR. AKS
 
 The Service network CIDR is the range of IP addresses reserved for Kubernetes services like LoadBalancers, ClusterIP, and NodePort within a cluster. Kubernetes supports the following service types:
 - ClusterIP: The default service type, which exposes the service within the cluster. The IP assigned from the Service network CIDR is only accessible within the Kubernetes cluster.
-- NodePort: Exposes the service on a specific port on each node’s IP address. The ClusterIP is still used internally, but external access is through the node IPs and a specific port.
+- NodePort: Exposes the service on a specific port on each node's IP address. The ClusterIP is still used internally, but external access is through the node IPs and a specific port.
 - LoadBalancer: This type creates a cloud-provider-managed load balancer and exposes the service externally. The cloud provider typically manages the external IP assignment, while the internal ClusterIP remains within the service network CIDR.
 
 AKS provides a **default value of 10.96.0.0/12** for the service network CIDR. AKS does not support customizations for the service network CIDR today.

AKS-Hybrid/aks-troubleshoot.md

@@ -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: 02/27/2024
+ms.date: 11/22/2024
 ms.author: sethm 
 ms.lastreviewed: 02/27/2024
 ms.reviewer: guanghu
@@ -16,7 +16,7 @@ This article describes how to find solutions for issues you encounter when using
 
 ## 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.
+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.
 
 ## Upgrade
 
@@ -28,5 +28,6 @@ If you continually see an [Azure Advisor](/azure/advisor/) upgrade recommendatio
 - 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.
 
 ## Next steps
+
 - [Troubleshoot K8sVersionValidation error](cluster-k8s-version.md)
 - [Use diagnostic checker](aks-arc-diagnostic-checker.md)

AKS-Hybrid/cluster-k8s-version.md

@@ -1,58 +1,52 @@
 ---
 title: Troubleshoot K8sVersionValidation error code
-description: Learn how to troubleshoot troubleshoot K8sVersionValidation error code
+description: Learn how to troubleshoot troubleshoot the K8sVersionValidation error code.
 ms.topic: troubleshooting
 author: sethmanheim
 ms.author: sethm
-ms.date: 10/02/2024
+ms.date: 11/22/2024
 ms.reviewer: abha
 
 ---
 
 # Troubleshoot K8sVersionValidation error code
 
-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.
+This article describes how to identify and resolve the K8sVersionValidation error code that occurs when you try to create and deploy an AKS cluster on Azure Local.
 
 ## Symptoms
 
 When you try to create an AKS Arc cluster, you receive one of the following error message(s):
 
-> "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"
-
-OR
-
-> 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.
-
-OR
-
-> Admission webhook \'vhybridakscluster.kb.io\' denied the request: Kubernetes version 1.26.12 is not available"
-
+- `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`
+- `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.`
+- `Admission webhook \'vhybridakscluster.kb.io\' denied the request: Kubernetes version 1.26.12 is not available`
 
 ## Error messages
 
-### 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
+This section describes the error messages that you might see when you encounter the K8sVersionValidation error code.
+
+### Kubernetes version 1.27.7 is not ready for use on Linux
 
-#### Linux VHD download has not completed
+This error message is caused by an incomplete Linux VHD download.
 
-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. 
+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. The error message can occur when your Linux VHD has not finished downloading. To resolve this issue, you should wait until your internet connection finishes downloading the Linux VHD image.
 
-To check if the image download is in progress or has finished, run the below command: 
+To check if the image download is in progress or finished, 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 using CLI (it automatically creates the **kubernetesVersions/default** Azure resource).
-
 az aksarc get-versions --custom-location $cl_id
 ```
 
-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).
+If this 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).
 
-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.**
+If you're running Azure Local release 2408 or older, proceed to the next section. We strongly recommend that you upgrade your Azure Local deployment to the latest version, in order to get the latest bug fixes and security updates.
 
-#### Recreate **kubernetesVersions/default** 
+#### Recreate kubernetesVersions/default
 
-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:
+If you redeploy Azure Local with the same name and parameters, you might have to recreate **kubernetesVersions/default**. To do so, run the following commands:
 
 ```azurecli
 $subscription = <subscription_id>
@@ -73,7 +67,7 @@ az rest --headers "Authorization=Bearer $token" "Content-Type=application/json;c
 az aksarc get-versions --custom-location $cl_id
 ```
 
-#### I cannot see the Kubernetes versions or VM size options on the Azure portal
+#### Can't see the Kubernetes versions or VM size options on the Azure portal
 
 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.
 
@@ -87,9 +81,9 @@ $cl_id = "/subscriptions/<subscription_id>/resourceGroups/<resource_group_name>/
 az aksarc get-versions --custom-location $cl_id
 ```
 
-### 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.
+### Kubernetes version 1.26.12 is not supported
 
-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.
+Azure Local supports specific Kubernetes versions in each of its releases. As stated in the error message, go to `https://aka.ms/aksarcsupportedversions` for a list of supported Kubernetes versions based on your deployed Azure Local release.
 
 ## Next steps
 

AKS-Hybrid/supported-kubernetes-versions.md

@@ -3,7 +3,7 @@ title: Supported Kubernetes versions for AKS enabled by Azure Arc
 description: Understand the Kubernetes version support policy and lifecycle of clusters for Azure Kubernetes Service enabled by Azure Arc.
 services: container-service
 ms.topic: article
-ms.date: 05/29/2024
+ms.date: 11/22/2024
 author: sethmanheim
 ms.author: sethm 
 ms.lastreviewed: 1/14/2022
@@ -16,7 +16,7 @@ ms.reviewer: abha
 
 # Supported Kubernetes versions in AKS Arc
 
-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.
+This article describes the supported Kubernetes versions for Azure Kubernetes Service enabled by Azure Arc. AKS Arc releases new Kubernetes minor versions approximately every three months.
 
 ## Kubernetes versions
 
@@ -36,11 +36,11 @@ Each number in the version indicates general compatibility with the previous ver
 * **Minor versions** change when functionality updates are made that are backwards compatible to the other minor releases.
 * **Patch versions** change when backwards-compatible bug fixes are made.
 
-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.
+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.
 
 ## AKS Arc Kubernetes release calendar
 
-View the current supported Kubernetes version releases on AKS Arc.
+The following table lists the current supported Kubernetes released versions on AKS Arc:
 
 |  K8s version | Supported Azure Local versions | Current status | Last release with Kubernetes patch/CVE updates |
 |--------------|-------------------|--------------|------------|
@@ -50,15 +50,14 @@ View the current supported Kubernetes version releases on AKS Arc.
 | 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 |
 | 1.26 | [2405](aks-whats-new-23h2.md#release-2405), 2402 and older | No more patch versions/CVE updates | 2405 release |
 
-
 ## Kubernetes version support policy
 
 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:
 
-* The latest GA minor version that is released for AKS (which we refer to as N).
+* The latest GA minor version that is released for AKS (referred to as *N*).
 * Two previous minor versions. Each supported minor version also supports stable patches.
 
-AKS might also support preview versions, which are explicitly labeled as such.
+AKS might also support preview versions, which are explicitly labeled as previews.
 
 > [!NOTE]
 > AKS uses safe deployment practices which involve gradual region deployment. This means it can take up to 10 business days for a new release or a new version to be available in all regions.
@@ -67,9 +66,9 @@ The supported window of Kubernetes versions on AKS is known as "N-2": (N (Latest
 
 For example, if AKS introduces **1.30** today, support is provided for the following versions:
 
-New minor version    |    Supported Version List
------------------    |    ----------------------
-1.30               |    1.30, 1.29, 1.28
+| New minor version    |    Supported Version List |
+| -----------------    |    ---------------------- |
+| 1.30               |    1.30, 1.29, 1.28 |
 
 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:
 
@@ -128,7 +127,7 @@ Specific patch releases may be skipped or rollout accelerated, depending on the
 
 ### How does Microsoft notify me of new Kubernetes versions?
 
-The AKS team publishes pre-announcements with planned dates of new Kubernetes versions in AKS Arc documentation.
+The AKS team publishes pre-announcements with planned dates of new Kubernetes versions in the AKS Arc documentation.
 
 ### How often should I expect to upgrade Kubernetes versions to stay in support?
 
@@ -139,7 +138,7 @@ Starting with Kubernetes 1.19, the [open source community expanded support to on
 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:
 
 * If the oldest supported Kubernetes version is 1.27 and you are on 1.26 or older, you're outside of support.
-* When you successfully upgrade from 1.26 to 1.27 or greater, you're back within our support policies.
+* When you successfully upgrade from 1.26 to 1.27 or greater, you're back within the support window.
 
 Downgrades are not supported.
 
@@ -148,7 +147,7 @@ Downgrades are not supported.
 "Outside of support" means that:
 
 * The version you're running is outside of the supported versions list.
-* You'll be asked to upgrade the cluster to a supported version when requesting support, unless you're within the 30-day grace period after version deprecation. 
+* You'll be asked to upgrade the cluster to a supported version when requesting support, unless you're within the 30-day grace period after version deprecation.
 
 Additionally, AKS doesn't make any runtime (or other) guarantees for clusters outside of the supported versions list.
 
@@ -158,26 +157,26 @@ For minor versions not supported by AKS, scaling in or out should continue to wo
 
 ### Can I skip multiple Kubernetes versions during a cluster upgrade?
 
-When you upgrade a supported AKS cluster, Kubernetes minor versions cannot be skipped. For example, upgrades between:
+When you upgrade a supported AKS cluster, Kubernetes minor versions can't be skipped. For example, upgrades between:
 
-* *1.12.x* -> *1.13.x*: allowed.
-* *1.13.x* -> *1.14.x*: allowed.
-* *1.12.x* -> *1.14.x*: not allowed.
+* **1.12.x** -> **1.13.x**: allowed.
+* **1.13.x** -> **1.14.x**: allowed.
+* **1.12.x** -> **1.14.x**: not allowed.
 
-To upgrade from *1.12.x* -> *1.14.x*:
+To upgrade from **1.12.x** -> **1.14.x**:
 
-1. Upgrade from *1.12.x* -> *1.13.x*.
-1. Upgrade from *1.13.x* -> *1.14.x*.
+1. Upgrade from **1.12.x** -> **1.13.x**.
+1. Upgrade from **1.13.x** -> **1.14.x**.
 
 You can only skip multiple versions when upgrading from an unsupported version back into a supported version. For example, you can upgrade from an unsupported 1.10.x to a supported 1.15.x.
 
 ### Can I create a new 1.xx.x cluster during its 30-day support window?
 
 No. Once a version is deprecated/removed, you cannot create a cluster with that version. As the change rolls out, you see the old version removed from your version list. This process can take up to two weeks from the announcement, progressively by region.
 
-### I am on a freshly deprecated version. Can I still add new node pools? Or do I have to upgrade?
+### I am on a freshly deprecated version. Can I still add new node pools, or do I have to upgrade?
 
-No. You can't add node pools of the deprecated version to your cluster.
+No. You can't add node pools from the deprecated version to your cluster.
 
 ## Next steps
 

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

@@ -4,14 +4,14 @@ description: Learn how to troubleshoot no VM sizes listed on Azure portal when y
 ms.topic: troubleshooting
 author: sethmanheim
 ms.author: sethm
-ms.date: 10/02/2024
+ms.date: 11/22/2024
 ms.reviewer: sumsmith
 
 ---
 
 # Troubleshoot no VM sizes listed on Azure portal when you create an AKS Arc cluster
 
-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.
+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.
 
 ## Workaround