Skip to content

Commit 6b4391c

Browse files
authored
Update scale-requirements.md
1 parent 92f2a14 commit 6b4391c

File tree

1 file changed

+24
-5
lines changed

1 file changed

+24
-5
lines changed

AKS-Arc/scale-requirements.md

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,19 +26,38 @@ This article describes the maximum and minimum supported scale count for AKS on
2626
| Number of node pools in an AKS cluster | 1 | 16 |
2727
| Number of nodes in a node pool (empty node pools not supported) | 1 | 64 |
2828
| Total number of nodes in an AKS cluster across nodepools | 1 | 200 |
29-
| Number of AKS clusters per Azure Local cluster | 0 |12 (8 GB ARB)<br>24 (16 GB ARB) |
29+
| Number of AKS clusters per Azure Local cluster | 0 | 32 |
3030

3131
## Concurrency for AKS enabled by Arc
3232

3333
| Scale item  | Count  |
3434
|-------------|--------|
35+
| Number of concurrent AKS cluster creations on an ARB  ||
36+
| Number of concurrent node pool creations on an ARB  ||
37+
| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pool or clusters  | 32 |
38+
| Number of long running operations that can be run simultaneously on an AKS cluster  | 1 per cluster. |
39+
40+
## Scale requirements when using autoscaler with AKS on Azure Local
41+
42+
> [!NOTE]
43+
> When autoscaler is enabled, Arc Resource Bridge (ARB) memory configuration determines the supported number of AKS clusters:
44+
> - **Up to 12 clusters** with an **8 GB ARB**
45+
> - **Up to 24 clusters** with a **16 GB ARB**
46+
>
47+
> If these limits are 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).
48+
>
49+
> If autoscaler is enabled on an environment that already exceeds these limits, performance may be impacted. Managing to supported limits is recommended.
50+
51+
To increase ARB memory and support additional clusters when using autoscaler, follow the resizing guide (link pending from Aline Tran).
52+
53+
| Scale item  | Count  |
54+
|-------------|--------|
55+
| Max Number of AKS clusters per Azure Local cluster | 12 (8 GB ARB)<br>24 (16 GB ARB) |
3556
| Number of concurrent AKS cluster creations on an ARB  ||
3657
| Number of concurrent node pool creations on an ARB  ||
37-
| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pool or clusters  |12 (8 GB ARB)<br>24 (16 GB ARB)  |
38-
| Number of long running operations that can be run simultaneously on an AKS cluster  | 1 per cluster.  |
58+
| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pool or clusters  | 12 (8 GB ARB)<br>24 (16 GB ARB)  |
3959

40-
> [!NOTE]
41-
> Each Arc Resource Bridge (ARB) supports a maximum number of AKS clusters based on its memory configuration (12 clusters for 8 GB ARB, 24 clusters for 16 GB ARB). Once these limits are reached, operations that add new clusters or node pools might not succeed. To manage capacity, consider deleting unused clusters using [az aksarc delete](/cli/azure/aksarc#az-aksarc-delete).
60+
Learn more about autoscaling with AKS on Azure Local [here](/azure/aks/aksarc/auto-scale-aks-arc).
4261

4362
## Default values for virtual machine sizes
4463

0 commit comments

Comments
 (0)