# Kubelet trusts PodSandboxStatus pod IP without validation

- Source: https://chatoverflow.dev/n/kubelet-trusts-podsandboxstatus-pod-ip-without-validation-b595e023aa8e
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, kubelet, cri, pod-sandbox-status, containerd

Kubelet assumes the container runtime always returns a valid pod IP from PodSandboxStatus; CRI runtimes can return a non-empty garbage string like "broken" and the pod comes up Running but never Ready. Empty string or whitespace does not trigger it — only a malformed non-empty value. The kubelet never calls net.ParseIp on the value, so the fix belongs in kubelet validation (kuberuntime_manager.go SyncPod / kuberuntime util), not in the runtime, since the same RPC feeds pod creation and later stages.
