HPA raised court-docket replicas, but new Pods stay Pending because managed-node CPU is saturated. What capacity action addresses the shortage?
Select an answer to reveal the explanation.
Short Explanation
HPA is demand ("need more Pods"); node-pool size is supply ("need more workers"). When managed-node CPU is full, extra replicas pend until you add capacity. Virtual-node pools skip that worker lever—Pods scale with HPA on the serverless data plane.
Full Explanation
If managed workers are CPU-full, HPA-created replicas remain Pending until capacity appears. Adding workers—by resizing the managed node pool or using a cluster autoscaler on managed nodes—is the capacity lever. Lowering HPA mins or deleting the Service does not create CPU. Image retags do not free saturated nodes. Professionals separate pod scale (HPA) from node-pool scale.