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: articles/aks/operator-best-practices-run-at-scale.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,16 +10,17 @@ ms.date: 10/04/2022
10
10
11
11
# Best practices for creating and running Azure Kubernetes Service (AKS) clusters at scale
12
12
13
-
AKS clusters that satisfy any of the below criteria should use the [Uptime SLA][Uptime SLA] feature for higher reliability and scalability of the Kubernetes control plan:
13
+
AKS clusters that satisfy any of the below criteria should use the [Standard tier with the Uptime SLA feature][standard-tier] for higher reliability and scalability of the Kubernetes control plane:
14
+
14
15
* Clusters running greater than 10 nodes on average
15
-
* Clusters that need to scale beyond 1000 nodes
16
+
* Clusters that need to scale beyond 1000 nodes
16
17
* Clusters running production workloads or availability sensitive mission critical workloads
17
18
18
-
To scale AKS clusters beyond 1000 nodes, you need to request a node limit quota increase by raising a support ticket via the [portal][Azure Portal] up-to a maximum of 5000 nodes per cluster.
19
+
To scale AKS clusters beyond 1000 nodes, you need to request a node limit quota increase by raising a support ticket in the [Azure Portal][Azure Portal] up-to a maximum of 5000 nodes per cluster.
19
20
20
21
To increase the node limit beyond 1000, you must have the following pre-requisites:
21
-
- An existing AKS cluster that needs the node limit increase. This cluster shouldn't be deleted as that will remove the limit increase.
22
-
-Uptime SLA enabled on your cluster.
22
+
23
+
-An existing AKS cluster in the Standard tier that needs the node limit increase. This cluster shouldn't be deleted as that will remove the limit increase.
23
24
- Clusters should use Kubernetes version 1.23 or above
24
25
25
26
> [!NOTE]
@@ -59,7 +60,7 @@ To increase the node limit beyond 1000, you must have the following pre-requisit
59
60
[Configure Azure CNI networking in Azure Kubernetes Service (AKS)]: configure-azure-cni.md#dynamic-allocation-of-ips-and-enhanced-subnet-support
0 commit comments