Skip to content

Commit 8d88169

Browse files
authored
add min/max limitation update
1 parent 456e934 commit 8d88169

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/aks/cluster-autoscaler.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,8 @@ az aks update \
9494

9595
The above example updates cluster autoscaler on the single node pool in *myAKSCluster* to a minimum of *1* and maximum of *5* nodes.
9696

97+
The cluster autoscaler will make its scaling decisions based on the minimum and maximum counts set on each node pool, but it does not enforce them. For example, setting a min-count of 5 when the current node count is 3 will not immediately scale the pool up to 5. If you change the minimum count on the node pool to a value higher than the current number of nodes, this new limit will be respected when there are unschedulable pods present that would require new nodes and trigger an autoscaler event.
98+
9799
> [!NOTE]
98100
> You can't set a higher minimum node count than is currently set for the node pool. For example, if you currently have min count set to *1*, you can't update the min count to *3*.
99101

0 commit comments

Comments
 (0)