Node group autoscaling in Managed Service for Kubernetes
The cluster autoscaler resizes the node group based on resource requests for the pods running on the nodes of that group.
How the autoscaler works
When creating a node group, you specify the minimum and maximum number of nodes in the group, and the Kubernetes cluster will check the status of pods and nodes from time to time:
- If pods cannot be assigned due to a lack of resources (vCPU, RAM) on the existing nodes, the number of nodes in the group will gradually increase to the specified maximum number.
- If the load on the nodes is insufficient, and all pods can be assigned with fewer nodes per group, the number of nodes per group will gradually decrease to the specified minimum number.
Warning
You can resize an autoscaling group using Kubernetes cluster-autoscaler, but there are many non-trivial features. If unexpected behavior occurs, we recommend referring to the FAQ. In particular:
- If you can distribute the load in a cluster to a smaller number of nodes, but you cannot evict pods from the nodes for some reason, the number of nodes in a group will not decrease.
- The actual number of nodes in a group may be below the minimum size of a node group. This may occur if:
- An autoscaled group resized up from its minimum size after being created.
- Actual cluster load does not require more nodes than the cluster currently has.
Note
When calculating the current limits and quotas, Managed Service for Kubernetes uses the specified maximum node group size as the actual size, regardless of the current group size.
The node group autoscaler is different from Horizontal Pod Autoscaler. The Horizontal Pod Autoscaler uses a controller to periodically request resource usage based on the metrics defined in each Kubernetes API HorizontalPodAutoscaler object. You can use both mechanisms in parallel.