Diagram
A four-step left-to-right flow showing traffic surge triggering HPA to add Pod replicas, scheduler attempting placement, and Cluster Autoscaler adding nodes only if Pods stay Pending, ending with Pending Pods scheduled.
How the Autoscalers Work Together
In a traffic surge, the flow moves from workload to infrastructure in order: first the HPA increases replicas, then the Kubernetes scheduler attempts to place the new Pods, and only after Pods remain Pending does the Cluster Autoscaler add nodes. The shared dependency for built-in workload scaling is Metrics Server, which retrieves container metrics from kubelets and exposes them through the Metrics API for the HPA and VPA to read.
Exam tip: The HPA changes Pod count, the VPA changes Pod size, and the Cluster Autoscaler changes node count; use the VPA for workloads that do not already use the HPA on the same CPU or memory metrics.
Domain 5 of 6
24 practice questions
Practice this DomainLast updated