Orchestrators
Kubernetes
Troubleshooting guide for Kubernetes alerting rules — nodes, pods, deployments, and resource pressure.
Alert runbooks (6)
A node is in NotReady state. Pods scheduled on it may be evicted or unreachable.
A pod's restart count is high. The container is repeatedly crashing and being restarted by kubelet.
A StatefulSet has fewer ready replicas than desired. One or more pods are not running or passing readiness checks.
A container was terminated by the Linux kernel's OOM killer because it exceeded its cgroup memory limit. Exit code 137 (SIGKILL) is recorded with Reason: OOMKilled.
A CronJob has been running longer than expected, or has stopped being scheduled entirely.
A node's available memory has fallen below the kubelet eviction threshold. The node is set to MemoryPressure=True, new pods are blocked from scheduling via the node.kubernetes.io/memory-pressure:NoSchedule taint, and running pods are being evicted to reclaim memory.