Diagram
A sequence showing traffic surge triggering Metrics Server, then HPA adding Pod replicas, then Scheduler leaving Pods Pending, then Cluster Autoscaler adding nodes so Pods can schedule.
Workload Scaling and Resource Optimization
Workload scaling in GKE automatically matches Pod and node capacity to traffic using separate controllers for replicas, container size, and nodes. The Horizontal Pod Autoscaler (HPA) changes replica count by scaling out when utilization stays above target and scaling in when it stays below target. Deployments must set CPU requests for measurement to work, with targets such as 70% or 80% leaving buffer for surges. The HPA scales on CPU and memory out of the box, on load balancer requests-per-second, or on custom metrics flowing from the application to Cloud Monitoring through the adapter to the HPA.
Domain 3 of 5
144 practice questions
Practice this DomainLast updated