Skip to main content

🧭 Alert when a Kubernetes node is NotReady

A node that is NotReady has a kubelet that stopped reporting or reports a problem, so Kubernetes stops sending it work.

🔎 Check it by hand​

  1. List the nodes
kubectl get nodes
  1. Read the node conditions and events. Look at Conditions and Events.
kubectl describe node <node>

🎯 What kwatch sends​

The message reads like this.

Example message​

🔴 Node n1 (prod-eu-1) has not reported for about two minutes. It reports "Kubelet stopped posting node status". kwatch cannot see why from inside the cluster: the kubelet stopped reporting, so the node may be down or unreachable. To check the node's conditions and recent events, run kubectl describe node n1

⭐ Which edition​

Community detects NotReady nodes. Node pressure and draining are Pro.

🚀 Install kwatch​

One command, and it walks you through it.

/bin/bash -c "$(curl -fsSL https://kwatch.dev/kwatch.sh)"

Community is free forever; Pro is free during early access. See Installation and Community vs Pro.