Pod running but never ready
The readiness probe keeps failing, the pod gets no traffic.
ImpactFewer serving replicas, rollout cannot progress
Can it be seen coming?No
RupturaNot covered yet
How to detect it
Pod running and not ready for a sustained time.
Metrics and signals to watch:
kube_pod_status_readyKubernetes event Unhealthy
Can you see it coming?
No This failure arrives without a reliable warning sign, so the goal is to detect it fast and explain it.
What it hits next
workload replicas, rollout.
What to do
Check what the probe tests, often a dependency or a slow start.
Sources
- kubernetes-mixin KubePodNotReady
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
- Memory leak ends in an OOM kill
- Memory growth accelerates toward the limit
- Sudden memory jump past the limit
- Container killed by OOM again and again
- Container crashes at start, again and again
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