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: modules/cluster-autoscaler-about.adoc
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,11 @@ The cluster autoscaler increases the size of the cluster when there are pods tha
15
15
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.
16
16
====
17
17
18
-
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.
18
+
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:
19
+
20
+
* 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.
21
+
* The cluster autoscaler can move all pods running on the node to the other nodes.
22
+
* The cluster autoscaler does not have scale down disabled annotation.
19
23
20
24
If the following types of pods are present on a node, the cluster autoscaler will not remove the node:
0 commit comments