Skip to content

Commit 0167a2f

Browse files
committed
update azure cni
1 parent 9011d20 commit 0167a2f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/aks/configure-azure-cni.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,9 @@ The maximum number of pods per node in an AKS cluster is 250. The *default* maxi
6363

6464
### Configure maximum - new clusters
6565

66-
You're able to configure the maximum number of pods per node *only at cluster deployment time*. If you deploy with the Azure CLI or with a Resource Manager template, you can set the maximum pods per node value as high as 250.
66+
You're able to configure the maximum number of pods per node at cluster deployment time or as you add new node pools. If you deploy with the Azure CLI or with a Resource Manager template, you can set the maximum pods per node value as high as 250.
67+
68+
If you don't specify maxPods when creating new node pools, you receive a default value of 30 for Azure CNI.
6769

6870
A minimum value for maximum pods per node is enforced to guarantee space for system pods critical to cluster health. The minimum value that can be set for maximum pods per node is 10 if and only if the configuration of each node pool has space for a minimum of 30 pods. For example, setting the maximum pods per node to the minimum of 10 requires each individual node pool to have a minimum of 3 nodes. This requirement applies for each new node pool created as well, so if 10 is defined as maximum pods per node each subsequent node pool added must have at least 3 nodes.
6971

0 commit comments

Comments
 (0)