PodDisruptionBudget blocks node maintenance
No disruption allowed, node drains hang.
ImpactUpgrades and maintenance stall
Can it be seen coming?Yes
RupturaNot covered yet
How to detect it
Zero disruptions allowed while a drain waits.
Metrics and signals to watch:
kube_poddisruptionbudget_status_pod_disruptions_allowed
Can you see it coming?
Yes Precursor: Replicas equal to minAvailable.
What it hits next
cluster upgrade.
What to do
Add replicas or relax the budget.
Sources
- Kubernetes PodDisruptionBudget
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
- Workload missing replicas
- StatefulSet missing replicas
- DaemonSet missing on some nodes
- Rollout passes its progress deadline
- New release leaks memory the previous one did not
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