You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AKS-Arc/scale-requirements.md
+23-4Lines changed: 23 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,16 +26,35 @@ This article describes the maximum and minimum supported scale count for AKS on
26
26
| Number of node pools in an AKS cluster | 1 | 16 |
27
27
| Number of nodes in a node pool (empty node pools not supported) | 1 | 64 |
28
28
| Total number of nodes in an AKS cluster across nodepools | 1 | 200 |
29
-
| Number of AKS clusters per Azure Local cluster | 0| 32 |
29
+
| Number of AKS clusters per Azure Local cluster | 0| 32 |
30
30
31
-
## Concurrency for AKS enabled by Arc
31
+
## Concurrency for AKS on Azure Local
32
32
33
33
| Scale item | Count |
34
34
|-------------|--------|
35
35
| Number of concurrent AKS cluster creations on an ARB | 8 |
36
36
| Number of concurrent node pool creations on an ARB | 8 |
37
-
| Number of concurrent operations across all different AKS clusters such as upgrade/scaling, etc., excluding creating node pool or clusters per ARB | 32 |
38
-
| Number of long running operations that can be run simultaneously on an AKS cluster | 1 per cluster. |
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, AKS on Azure Local currently supports a maximum of **12 clusters** per Azure Local environment.
44
+
>
45
+
> 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).
46
+
>
47
+
> If autoscaler is enabled in an environment that already exceeds the supported cluster count, performance may be impacted. Managing within supported limits is recommended.
48
+
49
+
| Scale item | Count |
50
+
|-------------|--------|
51
+
| Maximum number of AKS clusters with autoscaler enabled | 12 |
52
+
| Number of concurrent AKS cluster creations | 4 |
53
+
| Number of concurrent node pool creations | 4 |
54
+
55
+
Learn more about autoscaling with AKS on Azure Local [here](/azure/aks/aksarc/auto-scale-aks-arc).
56
+
57
+
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.
0 commit comments