Middle+

Нода в состоянии NotReady. Что делать?

sobes.tech AI

Answer from AI

If a Kubernetes node is in NotReady state, it means that kubelet on this node is not reporting its normal status to the cluster controllers. To resolve:

Check the node status:

kubectl describe node <node-name>

   Pay attention to events and error messages.

2. Check kubelet on the node itself:
   - Ensure that the kubelet service is running.
   - View kubelet logs:
     ```
journalctl -u kubelet -f

Check network settings and API server accessibility from the node.
Check the status of components that the node depends on (e.g., docker/containerd, CNI plugins).
If the issue is resource-related (e.g., lack of memory or disk), free up resources.
Restart kubelet or the node itself if necessary.
As a last resort, delete and re-register the node in the cluster.

Thus, diagnostics start with kubelet logs and status, then network and system resources are checked.

Previous Next