Kubernetes / Cluster Operations, Access & Incident Response
Investigate Node NotReady through conditions and recent events
An unready node can reflect runtime, network, kubelet or resource pressure rather than one application fault. Collect node evidence first.
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 describe node node01Read the result
The conditions, capacity and retained events describe the node's reported state. They may be stale if the kubelet cannot communicate with the API.
Resolve and verify
Correlate the first failed condition with host, runtime and network evidence through the cluster operator. Restore the dependency and verify node and workload readiness.
Before changing production
Do not reboot every node or delete the Node object before understanding workload placement and storage implications.