After joining a new county worker, nodes show Ready but pods on dif…

Question

After joining a new county worker, nodes show Ready but pods on different racks cannot reach each other. Firewall review shows VXLAN or CNI overlay ports between racks are closed. What does this pattern indicate?

Accepted Answer

Cross-node CNI dataplane traffic is blocked even though kubelet heartbeats succeed, so pod networking fails while node Ready remains true. — Ready just means the node's badge still scans at the door—it does not prove the overlay tunnel between buildings is open. Closed VXLAN or CNI ports leave pods stranded even when nodes look healthy.

Answer

The kube-scheduler is down, which always leaves nodes Ready but breaks all pod-to-pod connectivity.

Answer

etcd lost quorum, which keeps nodes Ready yet silently drops overlay packets between racks.

Answer

metrics-server is missing, so the CNI plugin refuses to program routes until CPU metrics return.

After joining a new county worker, nodes show Ready but pods on different racks cannot reach each other. Firewall review shows VXLAN or CNI overlay ports between racks are closed. What does this pattern indicate?

Short Explanation

Full Explanation