Kubernetes StatefulSet update not rolled out warning
>>>
max without (revision) (
kube_statefulset_status_current_revision
unless
kube_statefulset_status_update_revision
) * (
kube_statefulset_replicas
!=
kube_statefulset_status_replicas_updated
)
The expression finds any StatefulSet whose kube_statefulset_status_current_revision metric exists but the kube_statefulset_status_update_revision metric is absent (meaning an update is pending) and whose total replicas (kube_statefulset_replicas) differ from the number of replicas that have been updated (kube_statefulset_status_replicas_updated). If this condition is true for at least one StatefulSet (the max without (revision) yields a non‑zero value), the alert fires, indicating the update has not been fully rolled out.
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 PersistentVolume error
Kubernetes PersistentVolumeClaim pending
Kubernetes Pod not healthy
Kubernetes ReplicaSet replicas mismatch
Kubernetes StatefulSet down
Kubernetes StatefulSet generation mismatch
Kubernetes StatefulSet replicas mismatch
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