Failure catalog · pod level

Pod cannot be scheduled

Event FailedScheduling, no node fits its requests, affinity, taints or volumes.

ImpactThe pod stays Pending
Can it be seen coming?Partly
RupturaCovered

How to detect it

Event reason FailedScheduling.

Metrics and signals to watch:

Can you see it coming?

Partly Precursor: Requests growing toward node allocatable.

What it hits next

callers of the workload, rollout.

What to do

Free capacity, add nodes, or fix the constraints.

Sources

Where Ruptura stands

Ruptura reports this failure as the startup_stuck failure mode. A pre-registered lab test is not published yet.

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