Seeing a NotReady
node can impact pod scheduling and cluster stability.
Steps to Fix:
- Check node status:
kubectl get nodes
- SSH into the node:
- Run
systemctl status kubelet
- Check disk space:
df -h
- Inspect network: is DNS working?
- Run
- Use:
journalctl -u kubelet
to see kubelet errors.
Resolution:
- Restart kubelet or the node VM
- Clear disk if full
- Reconfigure cloud provider settings (e.g., IAM roles, security groups)