Image cannot be pulled
ErrImagePull then ImagePullBackOff, the tag does not exist, the registry refuses, or the secret is wrong.
ImpactThe pod never starts
Can it be seen coming?No
RupturaCovered and tested on the lab
How to detect it
Event message ErrImagePull or ImagePullBackOff.
Metrics and signals to watch:
Kubernetes events Failed and BackOffkube_pod_container_status_waiting_reason
Can you see it coming?
No Precursor: None, a new image reference is the cause. This failure arrives without a reliable warning sign, so the goal is to detect it fast and explain it.
What it hits next
callers of the workload, rollout.
What to do
Fix the image reference or the pull secret.
Sources
- kubernetes-mixin KubeContainerWaiting
- Kubernetes waiting reason ImagePullBackOff
Where Ruptura stands
Ruptura reports this failure as the startup_stuck failure mode, and it is measured by a pre-registered test on the lab.
Related failures
- Image name is not valid
- Volume cannot be mounted
- Volume cannot be attached to the node
- Pod cannot be scheduled
- 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