Failure catalog · workload level

Autoscaler at its maximum

The HorizontalPodAutoscaler wants more replicas than its maximum.

ImpactLoad beyond capacity, latency and errors rise
Can it be seen coming?Yes
RupturaNot covered yet

How to detect it

Current replicas at maximum for a sustained time.

Metrics and signals to watch:

Can you see it coming?

Yes Precursor: Replica count climbing toward the maximum with daily load.

What it hits next

callers of the workload.

What to do

Raise the maximum, add capacity, or reduce load per request.

Sources

Where Ruptura stands

Ruptura does not cover this failure yet. The card is here so you know it exists and how to detect it.

Related failures

This card is part of an open catalog of 66 Kubernetes and OpenShift failures. Correct it or add one on GitHub.

See it coming instead of reading about it
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub