Kubernetes DaemonSet misscheduled critical
>>>
kube_daemonset_status_number_misscheduled
> 0
The query checks the metric kube_daemonset_status_number_misscheduled, which reports how many pods of a DaemonSet are running on nodes they shouldn't be. The alert fires whenever this value is greater than zero, meaning at least one pod is misscheduled for the indicated DaemonSet ($labels.namespace/$labels.daemonset).
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 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 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