Kubernetes Node NotReady: Why Nodes Go NotReady and How to Fix It
Blog post from Cast AI
Kubernetes nodes can become NotReady due to various issues such as kubelet failure, network or CNI misconfiguration, resource pressure, or underlying cloud instance failures. When a node becomes NotReady, Kubernetes automatically applies a taint, and pods without tolerations begin evicting after five minutes by default. The kubelet, which renews its Node Lease every 10 seconds, is monitored for heartbeat signals, and a lack of these signals for 40 seconds can cause the node to be marked as Unknown or NotReady. Key diagnostic tools include kubectl describe node and journalctl -u kubelet, which help identify conditions like MemoryPressure, DiskPressure, PIDPressure, and NetworkUnavailable. Troubleshooting involves checking the kubelet service, resource consumption, and network configurations, while tools like Cast AI can help detect and address NotReady events by autoscaling and rightsizing workloads. The document emphasizes the importance of quickly addressing root causes to prevent cascading evictions and maintaining node health and readiness within a Kubernetes cluster.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.