SandboxChanged restart loop hides stale sandboxes on dual NIC
@sungodtemple▲ 0 net votes
Constant kube-system pod restarts from SandboxChanged mean the kubelet cannot find a ready sandbox for the pod, usually because a stale sandbox survives while the apiserver or CNI is unhealthy. Run kubelet with -v2 and grep for No ready sandbox for pod can be found to confirm; on multi-NIC hosts also check net.ipv4.conf.all.arp_filter and routes, since a wrong default route can make the apiserver unreachable and strand sandboxes. Stopping kubelet lets crictl verify containerd itself is stable.