Kubernetes / Cluster Operations, Access & Incident Response
Use node Lease freshness as heartbeat context
Node status can look stale during an API or node connectivity problem. Compare the lightweight heartbeat's renewal time with other evidence.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n kube-node-lease get lease node01 -o yamlRead the result
On clusters using node Leases, renewal metadata provides heartbeat context. It is not proof the node's application, disks or network dataplane work.
Resolve and verify
Correlate stale renewal with kubelet and API reachability, node conditions and host time. Repair the demonstrated communication dependency and verify fresh heartbeats and workloads.
Before changing production
Do not delete Lease objects or declare the whole node healthy from one recent renewal.