Recycling-schedule API traffic spikes at evening set-out times. Operators want more Pods automatically when CPU rises. Which object changes the Deployment replica count?
Select an answer to reveal the explanation.
Short Explanation
HPA is the thermostat for replica count: watch CPU (or a custom metric), then dial Pods up or down. That is pod-level scale—not an email-only Monitoring alarm, and not a PDB freeze. On virtual-node pools, HPA scales Pods; you do not also stand up a node autoscaler for that pool.
Full Explanation
A Horizontal Pod Autoscaler adjusts a Deployment's replica count from a metric such as CPU or a custom metric. That is demand-driven pod scale. An OCI Monitoring alarm that only notifies humans does not change replicas by itself. PodDisruptionBudgets constrain voluntary disruptions; they are not autoscalers. Official virtual-node guidance: use HPA for pods; do not also run a node autoscaler against that virtual pool.