Container cannot start because of its configuration
Waiting reason CreateContainerConfigError, a ConfigMap, Secret or key is missing.
ImpactThe pod never starts
Can it be seen coming?No
RupturaNot covered yet
How to detect it
Waiting reason CreateContainerConfigError.
Metrics and signals to watch:
kube_pod_container_status_waiting_reason
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
callers of the workload.
What to do
Create the missing ConfigMap or Secret, or fix the reference.
Sources
- kubernetes-mixin KubeContainerWaiting
- Kubernetes waiting reason CreateContainerConfigError
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