Kubernetes / Services, DNS & Traffic Routing
Investigate Pod sandbox creation failures before changing application images
A Pod can fail before the application starts because the runtime cannot establish its network sandbox. Inspect the precise node-side event.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app describe pod web-0Read the result
FailedCreatePodSandBox events can name a network plugin or runtime problem. The application logs may not exist because its container never started.
Resolve and verify
Correlate the event with node runtime and CNI component evidence through the cluster owner. Repair the supported plugin, IP allocation or node dependency and validate a replacement.
Before changing production
Do not delete plugin state directories or reinstall CNI blindly on a live node.