jargon

Platform & DevOps·Placement, resources and the pod lifecycle

traffic doubled and the replica count went from four to nine on its own, a minute or two after it needed to.

Horizontal autoscaling

Also calledHPA, horizontal pod autoscaler, replica autoscaling

Adding and removing copies of a workload automatically based on a metric — CPU, memory, queue depth, request rate. It is the standard elasticity mechanism and it works well for stateless request handlers whose load metric is honest. Its two constant problems are lag, because the metric arrives after the traffic did, and flapping, which is why cooldown windows exist and why a scale signal tied to a lagging indicator makes things worse.

Commonly confused with