Workload missing replicas
Fewer available replicas than desired for a sustained time.
ImpactLess capacity, no redundancy left
Can it be seen coming?No
RupturaCovered
How to detect it
Desired minus available above zero for 5 minutes.
Metrics and signals to watch:
kube_deployment_spec_replicaskube_deployment_status_replicas_available
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
Check why the missing pods are not ready.
Sources
- kubernetes-mixin KubeDeploymentReplicasMismatch
Where Ruptura stands
Ruptura reports this failure as the replicas_unavailable failure mode. A pre-registered lab test is not published yet.
Related failures
- StatefulSet missing replicas
- DaemonSet missing on some nodes
- Rollout passes its progress deadline
- New release leaks memory the previous one did not
- Autoscaler at its maximum
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