Kubernetes PersistentVolume error critical
>>>
kube_persistentvolume_status_phase
{phase=~"Failed|Pending", job="kube-state-metrics"} > 0
The query returns the count of persistent volumes whose phase label matches Failed or Pending as reported by kube-state-metrics. The alert fires whenever this count is greater than zero, i.e., when at least one PV is in a Failed or Pending state.
Exporters Used
Related Alerts
Kubernetes API client errors
Kubernetes API server errors
Kubernetes API server latency
Kubernetes Container oom killer
Kubernetes CronJob suspended
Kubernetes CronJob too long
Kubernetes DaemonSet misscheduled
Kubernetes DaemonSet rollout stuck
Kubernetes Deployment generation mismatch
Kubernetes Deployment replicas mismatch
Kubernetes HPA metrics unavailability
Kubernetes HPA scale inability
Kubernetes HPA scale maximum
Kubernetes HPA underutilized
Kubernetes Job failed
Kubernetes Job not starting
Kubernetes Job slow completion
Kubernetes Node disk pressure
Kubernetes Node memory pressure
Kubernetes Node network unavailable
Kubernetes Node not ready
Kubernetes Node out of pod capacity
Kubernetes Node scheduling disabled
Kubernetes PersistentVolumeClaim pending
Kubernetes Pod not healthy
Kubernetes ReplicaSet replicas mismatch
Kubernetes StatefulSet down
Kubernetes StatefulSet generation mismatch
Kubernetes StatefulSet replicas mismatch
Kubernetes StatefulSet update not rolled out
Kubernetes Volume full in four days
Kubernetes Volume out of disk space
Kubernetes client certificate expires next week
Kubernetes client certificate expires soon
Kubernetes pod crash looping