Merge pull request #17843 from sethmanheim/autosc

Update submissions:

Author: prmerger-automator[bot]

AKS-Arc/auto-scale-aks-arc.md

@@ -5,9 +5,9 @@ ms.topic: how-to
 ms.custom: devx-track-azurecli
 author: sethmanheim
 ms.author: sethm
-ms.date: 08/01/2024
+ms.date: 05/02/2025
 ms.reviewer: abha
-ms.lastreviewed: 08/01/2024
+ms.lastreviewed: 05/02/2025
 
 # Intent: As a Kubernetes user, I want to use cluster autoscaling to grow my nodes to keep up with application demand.
 # Keyword: cluster autoscaling Kubernetes
@@ -19,8 +19,8 @@ ms.lastreviewed: 08/01/2024
 
 To keep up with application demands in Kubernetes, you might need to adjust the number of nodes that run your workloads. The cluster autoscaler component watches for pods in your cluster that can't be scheduled because of resource constraints. When the cluster autoscaler detects issues, it scales up the number of nodes in the node pool to meet the application demands. It also regularly checks nodes for a lack of running pods and scales down the number of nodes as needed. This article shows you how to enable and manage the cluster autoscaler in AKS Arc.
 
->[!NOTE]
->Before enabling autoscaling on your Azure Local cluster, review the [Scale requirements for AKS on Azure Local](/azure/aks/aksarc/scale-requirements#scale-requirements-when-using-autoscaler-with-aks-on-azure-local) to ensure your environment meets the necessary limits.
+> [!NOTE]
+> Before enabling autoscaling on your Azure Local cluster, review the [Scale requirements for AKS on Azure Local](/azure/aks/aksarc/scale-requirements#scale-requirements-when-using-autoscaler-with-aks-on-azure-local) to ensure your environment meets the required limits.
 
 ## Enable the cluster autoscaler on a new cluster
 

AKS-Arc/scale-requirements.md

@@ -2,7 +2,7 @@
 title: Scale requirements for AKS on Azure Local
 description: Learn about scale requirements for AKS on Azure Local.
 ms.topic: conceptual
-ms.date: 03/25/2025
+ms.date: 05/02/2025
 author: sethmanheim
 ms.author: sethm 
 ms.reviewer: abha
@@ -25,7 +25,7 @@ This article describes the maximum and minimum supported scale count for AKS on
 | Number of nodes in default node pool created during cluster create  | 1 | 200 |
 | Number of node pools in an AKS cluster  | 1  | 16  |
 | Number of nodes in a node pool (empty node pools not supported)  | 1 | 64 |
-| Total number of nodes in an AKS cluster across nodepools | 1 | 200 |
+| Total number of nodes in an AKS cluster across node pools | 1 | 200 |
 | Number of AKS clusters per Azure Local cluster | 0 | 32 |
 
 ## Concurrency for AKS on Azure Local
@@ -34,27 +34,25 @@ This article describes the maximum and minimum supported scale count for AKS on
 |-------------|--------|
 | Number of concurrent AKS cluster creations on an ARB  | 8 |
 | Number of concurrent node pool creations on an ARB  | 8  |
-| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pool or clusters  | 32 |
-| Number of long running operations that can be run simultaneously on an AKS cluster  | 1 per cluster. |
+| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pools or clusters  | 32 |
+| Number of long running operations that can be run simultaneously on an AKS cluster  | 1 per cluster |
 
 ## Scale requirements when using autoscaler with AKS on Azure Local
 
 > [!NOTE]
-> When autoscaler is enabled, AKS on Azure Local currently supports a maximum of **12 clusters** per Azure Local environment.
+> When the autoscaler is enabled, AKS on Azure Local currently supports a maximum of 12 clusters per Azure Local environment. If this limit is exceeded, operations such as creating additional clusters or node pools might not succeed. To manage capacity, we recommend deleting unused clusters using the [az aksarc delete](/cli/azure/aksarc#az-aksarc-delete) command.
 >
-> If this limit is exceeded, operations such as creating additional clusters or node pools may not succeed. To manage capacity, we recommend deleting unused clusters using [az aksarc delete](/cli/azure/aksarc#az-aksarc-delete).
->
-> If autoscaler is enabled in an environment that already exceeds the supported cluster count, performance may be impacted. Managing within supported limits is recommended.
+> If the autoscaler is enabled in an environment that already exceeds the supported cluster count, performance might be impacted. Managing within supported limits is recommended.
 
 | Scale item  | Count  |
 |-------------|--------|
 | Maximum number of AKS clusters with autoscaler enabled | 12 |
 | Number of concurrent AKS cluster creations | 4 |
 | Number of concurrent node pool creations | 4 |
 
-Learn more about autoscaling with AKS on Azure Local [here](/azure/aks/aksarc/auto-scale-aks-arc).
+For more information, see [autoscaling with AKS on Azure Local](/azure/aks/aksarc/auto-scale-aks-arc).
 
-If you're operating at enterprise scale and have scenarios that require higher cluster counts with autoscaler enabled, reach out to your Microsoft account team or support to discuss potential options.
+If you operate at enterprise scale and have scenarios that require higher cluster counts with the autoscaler enabled, contact your Microsoft account team or support to discuss potential options.
 
 ## Default values for virtual machine sizes