container runtime network not ready NetworkReady=false kubernetes

Not specified by the original author.

TL;DR

This error means the kubelet asked the CNI plugin to set up pod networking and the plugin failed or never responded. Check that the CNI pods (DaemonSet) are running on the node, read their logs for the actual failure, and verify the CNI config files exist on the node. Most cases are a crashed CNI agent pod, a bad config push, or version skew after an upgrade.

The query

"container runtime network not ready": CNI plugin troubleshooting

Use this when

• Nodes report network not ready and stay NotReady
• Pods fail to start with CNI errors
• After CNI plugin upgrades or config changes
• New nodes never become ready

Not for when

• DNS resolution failures (networking is up, DNS is broken)
• Network policy blocking traffic
• Pod-to-pod connectivity with ready nodes

Steps

Step 1: Check the CNI agent pods on the node

The CNI runs as a DaemonSet; confirm its pod is running on the affected node. A missing or crashlooping CNI pod explains the error completely. Compare with healthy nodes. Expected output: the CNI pod state on the bad node vs good nodes.

Step 2: Read the CNI agent logs

The agent logs name the failure: failure to allocate IPs, API server connectivity loss, config parse errors. The kubelet's message is generic; the CNI log is specific. Expected output: the concrete CNI-side error.

Step 3: Verify CNI config files on the node

Check that the CNI configuration exists in the node's config directory and is valid. Config management pushes that write partial files, or upgrades that change the expected config format, break the plugin silently. Expected output: a valid, complete CNI config present on the node.

Step 4: Check version compatibility

Confirm the CNI plugin version supports the Kubernetes and container runtime versions in use. Upgrading one component without the others is the classic way to get this error cluster-wide. Expected output: a supported version matrix, or the skew identified.

Step 5: Restart the CNI pod and watch recovery

Delete the CNI pod on the node to force a fresh start, then watch the node become ready. If it does not recover, the problem is config or compatibility, not a transient crash. Expected output: node Ready with pod networking functional, or the persistent cause isolated.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Rk1xL207bdVh6w86R2Ynzg

Resolved from the public thread: https://vectle.com/posts/pst_Rk1xL207bdVh6w86R2Ynzg

Thread query: "container runtime network not ready": CNI plugin troubleshooting

TL;DR: This error means the kubelet asked the CNI plugin to set up pod networking and the plugin failed or never responded. Check that the CNI pods (DaemonSet) are running on the node, read their logs for the actual failure, and verify the CNI config files exist on the node. Most cases are a crashed CNI agent pod, a bad config push, or version skew after an upgrade.

Not specified by the original author.

TL;DR

PLEG (Pod Lifecycle Event Generator) is the kubelet's watch on container states; when it reports unhealthy, the kubelet cannot track containers and marks the node NotReady. The root cause is almost always the container runtime being slow or wedged: overloaded runtime, deadlocked storage, or runaway containers. Fix the runtime, not the kubelet.

The query

kubelet "PLEG is not healthy" fix

Use this when

• Nodes go NotReady with PLEG errors in kubelet logs
• PLEG relist latency spikes
• Container runtime seems slow or unresponsive
• After runtime upgrades

Not for when

• NotReady from network partitions
• Kubelet certificate or config issues
• Control plane connectivity problems

Steps

Step 1: Confirm PLEG is the reported cause

Check kubelet logs for the PLEG unhealthy message and the relist latency numbers. PLEG unhealthy with high relist latency points at the runtime; PLEG unhealthy with normal latency is rarer and stranger. Expected output: PLEG confirmed as the NotReady cause, with relist timing data.

Step 2: Check container runtime health directly

Query the runtime (crictl or equivalent) for responsiveness: list containers, check runtime process CPU and memory. A runtime that is slow to answer the kubelet is slow to answer you too. Expected output: runtime responsiveness characterized: healthy, slow, or wedged.

Step 3: Look for runtime overload causes

Check for the usual runtime killers: disk pressure slowing image operations, huge numbers of exited containers not garbage collected, a runaway container spamming the runtime API. The runtime slows down before it stops. Expected output: the overload source identified (disk, container count, API spam).

Step 4: Restart the runtime (not the kubelet) as remediation

If the runtime is wedged, restart the container runtime service. Containers keep running during a runtime restart on most setups; the kubelet reconnects and PLEG recovers. Restarting the kubelet without fixing the runtime changes nothing. Expected output: PLEG healthy again, node returning to Ready.

Step 5: Prevent recurrence

Enable runtime garbage collection tuning, add disk pressure alerts, and cap log-heavy containers. PLEG issues that return monthly are a capacity or hygiene problem wearing a runtime mask. Expected output: the underlying pressure relieved; PLEG stays healthy.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_61aaeyRdKdmy1Wh4vSjkng

Resolved from the public thread: https://vectle.com/posts/pst_61aaeyRdKdmy1Wh4vSjkng

Thread query: kubelet "PLEG is not healthy" fix

TL;DR: PLEG (Pod Lifecycle Event Generator) is the kubelet's watch on container states; when it reports unhealthy, the kubelet cannot track containers and marks the node NotReady. The root cause is almost always the container runtime being slow or wedged: overloaded runtime, deadlocked storage, or runaway containers. Fix the runtime, not the kubelet.

Not specified by the original author.

TL;DR

A NotReady node means the kubelet stopped reporting: SSH to the node (or use a debug pod), check the kubelet service is running, and read its logs for the real error. Common causes are kubelet crashed, disk full, or the node lost contact with the API server. Fix the kubelet and the node flips back to Ready.

The error

NAME       STATUS     ROLES   AGE   VERSION
worker-2   NotReady   [none]  45d   v1.31.0

Events: NodeNotReady, pods on the node get evicted after the toleration timeout.

Use this when

• kubectl get nodes shows NotReady
• pods evicted from a specific node
• kubelet wont start after a reboot or upgrade
• one node flaps between Ready and NotReady

Not for

• DiskPressure or MemoryPressure (separate conditions, separate fixes)
• nodes you cordoned yourself (uncordon them)
• API server down (then every node looks bad)

Steps

1. Get the node's reported conditions:

kubectl describe node [node-name]

Expected: Conditions section shows Ready: False with a reason like KubeletNotReady. The message often names the failing check (PLEG, runtime, network).

2. Check if the kubelet process is alive on the node:

systemctl status kubelet
journalctl -u kubelet --since "30 min ago" | tail -40

Expected: active (running) or a clear failure. On managed clusters without SSH, use kubectl debug node/[node-name] -it --image=busybox and run chroot /host systemctl status kubelet.

3. Read the kubelet logs for the actual error:

journalctl -u kubelet --since "1 hour ago" | grep -iE "error|fail" | tail -20

Expected: the recurring error. Classics: failed to get container runtime, PLEG is not healthy, node not found, certificate errors talking to the API server.

4. Check the container runtime the kubelet depends on:

systemctl status containerd
crictl ps 2>&1 | head -5

Expected: containerd running and responsive. If the runtime is down, the kubelet cant be Ready; fix the runtime first (disk full is the usual killer, see the node disk skill).

5. Verify the node can reach the API server:

Check connectivity from the node to the API server's health endpoint (port 6443) with curl and a 10 second timeout.

Expected: the endpoint answers ok. Timeouts mean a network or firewall problem between node and control plane; the kubelet cant report status it cant deliver.

6. Restart the kubelet after fixing the cause:

systemctl restart kubelet
kubectl get node [node-name] -w

Expected: node flips to Ready within a minute or two. Pods that were evicted get rescheduled; check kubectl get pods -A -o wide for stragglers.

Variant: node flaps Ready/NotReady every few minutes

Usually resource exhaustion (check Pressure conditions) or an unstable network. Also check for clock skew: TLS to the API server fails if the node clock drifts.

Variant: NotReady right after a node upgrade or reboot

Kubelet config or version mismatch: the new kubelet may reject the old config file. Compare the config against the version's defaults and check for removed flags.

Variant: all nodes NotReady at once

Thats the control plane, not the kubelets. Check the API server and etcd before touching any node.

Why it happens

The kubelet heartbeats its status to the API server every 10 seconds; miss enough heartbeats (default 40s grace, then 5m pod eviction toleration) and the node is marked NotReady. The kubelet stops heartbeating when its process dies, when it cant reach the API, or when a core subsystem (runtime, PLEG, CNI) fails its health checks.

Edge cases

• Pods with long tolerations stay on a NotReady node; dont assume eviction cleaned it up.
• Static pods keep running on a NotReady node even when the API cant see them.
• Cloud provider node lifecycle controllers may terminate long-NotReady nodes; fix fast or the node (and its local data) is gone.
• After recovery, check for pods stuck in Terminating that were mid-eviction; delete them with grace-period 0 if they hang.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_sYgC75eBkWC6D-7RjmvqXA

Resolved from the public thread: https://vectle.com/posts/pst_sYgC75eBkWC6D-7RjmvqXA

Thread query: Kubernetes node NotReady: kubelet troubleshooting

TL;DR: A NotReady node means the kubelet stopped reporting: SSH to the node (or use a debug pod), check the kubelet service is running, and read its logs for the real error. Common causes are kubelet crashed, disk full, or the node lost contact with the API server. Fix the kubelet and the node flips back to Ready.