Merge pull request #57995 from xenolinux/autoscaler

Author: adellape

modules/cluster-autoscaler-about.adoc

@@ -29,7 +29,7 @@ Ensure that the `maxNodesTotal` value in the `ClusterAutoscaler` resource defini
 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:
 
 * The node utilization is less than the _node utilization level_ threshold for the cluster. The node utilization level is the sum of the requested resources divided by the allocated resources for the node. If you do not specify a value in the `ClusterAutoscaler` custom resource, the cluster autoscaler uses a default value of `0.5`, which corresponds to 50% utilization.
-* The cluster autoscaler can move all pods running on the node to the other nodes.
+* The cluster autoscaler can move all pods running on the node to the other nodes. The Kubernetes scheduler is responsible for scheduling pods on the nodes.
 * The cluster autoscaler does not have scale down disabled annotation.
 
 If the following types of pods are present on a node, the cluster autoscaler will not remove the node:
@@ -58,6 +58,8 @@ The cluster autoscaler takes pod priorities into account. The Pod Priority and P
 
 Pods with priority lower than the cutoff value do not cause the cluster to scale up or prevent the cluster from scaling down. No new nodes are added to run the pods, and nodes running these pods might be deleted to free resources.
 
+Cluster autoscaling is supported for the platforms that have machine API available on it.
+
 ////
 Default priority cutoff is 0. It can be changed using `--expendable-pods-priority-cutoff` flag, but we discourage it. cluster autoscaler also doesn't trigger scale-up if an unschedulable Pod is already waiting for a lower priority Pod preemption.
 ////