Worker nodes
Heartbeats
33 / 82

A missed heartbeat marks a node Unknown first, and evicts only after a grace period.

The two-stage timeout stops a brief network blip from rescheduling every Pod on a perfectly healthy node.

Timeline after the last heartbeat (default values)Healthykubelet updates node status about every 10 s~40 s: Ready = Unknownnode controller marks it, adds taintsgrace period: 5 min tolerationPods tolerate the not-ready taint for 300 sEvict and reschedulecontrollers recreate Pods

Node conditions are separate signals

Readykubelet is healthy and can accept Pods
MemoryPressurelow memory: kubelet may evict Pods
DiskPressurelow disk or inodes: eviction possible
PIDPressuretoo many processes
NetworkUnavailableCNI not yet configured, often right after join
inspect a node
$ kubectl describe node gke-np1-x2 | \
    sed -n '/Conditions/,/Addresses/p'
Ready            True   KubeletReady
MemoryPressure   False
DiskPressure     False
PIDPressure      False
$ kubectl get lease -n kube-node-lease