PersistentVolumeClaim stays Pending
No volume binds, the storage class cannot provision.
ImpactPods that need the claim never start
Can it be seen coming?No
RupturaNot covered yet
How to detect it
Phase Pending for a sustained time.
Metrics and signals to watch:
kube_persistentvolumeclaim_status_phase
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
pods using the claim.
What to do
Check the storage class, its provisioner and capacity.
Sources
- Kubernetes PersistentVolumeClaim phase
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
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