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:
Kubernetes event FailedSchedulingkube_pod_status_unschedulable
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
- kubernetes-mixin KubePodNotReady
- Kubernetes event reason FailedScheduling
Where Ruptura stands
Ruptura reports this failure as the startup_stuck failure mode. A pre-registered lab test is not published yet.
Related failures
- Image cannot be pulled
- Image name is not valid
- Volume cannot be mounted
- Volume cannot be attached to the node
- Pod sandbox cannot be created
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
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