Skip to content

Commit 40d403b

Browse files
authored
Merge pull request #38894 from xenolinux/BZ22
Add info on how the cluster autoscaler works
2 parents d7c87ea + c6f23ca commit 40d403b

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

modules/cluster-autoscaler-about.adoc

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,11 @@ The cluster autoscaler computes the total memory, CPU, and GPU on all nodes the
1717
Ensure that the `maxNodesTotal` value in the `ClusterAutoscaler` resource definition that you create is large enough to account for the total possible number of machines in your cluster. This value must encompass the number of control plane machines and the possible number of compute machines that you might scale to.
1818
====
1919

20-
The cluster autoscaler decreases the size of the cluster when some nodes are consistently not needed for a significant period, such as when it has low resource use and all of its important pods can fit on other nodes.
20+
Every 10 seconds, the cluster autoscaler checks which nodes are unnecessary in the cluster and removes them. The cluster autoscaler considers a node for removal if the following conditions apply:
21+
22+
* The sum of CPU and memory requests of all pods running on the node is less than 50% of the allocated resources on the node.
23+
* The cluster autoscaler can move all pods running on the node to the other nodes.
24+
* The cluster autoscaler does not have scale down disabled annotation.
2125

2226
If the following types of pods are present on a node, the cluster autoscaler will not remove the node:
2327

0 commit comments

Comments
 (0)