Container Startup
18 incident problems about Container Startup. Start with the reviewed ones.
Read first
When the ConfigMap changed but the Pod keeps using the old valuesAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when values don't refresh after a ConfigMap update because of envFrom, subPath, volume projection, or rollout trigger differences.Kubernetes3 min readWhen CoreDNS is Running but only DNS lookups failAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when the CoreDNS Pod looks healthy but failures occur in the kube-dns path, upstream, node-local-dns, or policy.Kubernetes3 min readWhat to check first when CrashLoopBackOff appearsAn InfraTree guide that lays out the first signals to check, the CLI verification order, common misdiagnoses, and a safe recovery path when a Pod restarts repeatedly and the real cause is left in the previous logs and events.Kubernetes3 min read
Recommended problems
Reviewed problems first, then problems with detailed scenarios.
K8S-1192Core application restarts endlesslyA public probe example was copied into production. It worked in steady state, but after a cold deploy the app now gets killed before it can finish bootstrap.ReviewedKubernetesAdvanced21 minFreeImagePullBackOff: new pods cannot pull the release imageImagePullBackOff: new pods cannot pull the release image is a hands-on troubleshooting drill. Read the pull event to see what the registry could not find. container-startup needs to be checked by narrowing scope, recent change, and the current live signal before rollback. 실무에서...ReviewedKubernetesBeginner3 minFree
All problems (18)
ImagePullBackOff: new pods cannot pull the release imageImagePullBackOff: new pods cannot pull the release image is a hands-on troubleshooting drill. Read the pull event to see what the registry could not find. container-startup needs to be checked by narrowing scope, recent change, and the current live signal before rollback. 실무에서...ReviewedKubernetesBeginner3 minFreeK8S-1192Core application restarts endlesslyA public probe example was copied into production. It worked in steady state, but after a cold deploy the app now gets killed before it can finish bootstrap.ReviewedKubernetesAdvanced21 minFreeK8S-1235An init job fixes permissions but the main container still failsA pod initializes successfully on some restarts and fails on others depending on the relative timing of the CSI mount and init logic.KubernetesIntermediate18 minProK8S-1216Init container looks correct but still reads an empty secret fileA pod boots through an init step that reads a mounted secret and fails only on cold starts.KubernetesAdvanced18 minProK8S-1220Pod restarts stop after raising memory, but rollout still failsA team fixes the direct crash cause and still cannot complete rollout because the health timing contract was never updated.KubernetesAdvanced18 minProK8S-1213PVC is bound but the pod still misses rollout windowsA stateful workload gets its PVC but still appears hung every time it starts.KubernetesAdvanced20 minProK8S-1228A ConfigMap key exists but the app still crashesAn application restart was skipped because the team expected the mounted config file to update in place after a ConfigMap edit.KubernetesIntermediate17 minProK8S-1233A projected secret file exists but the app still sees the old valueA workload updates a secret successfully, yet the application keeps reading the initial secret value until a full restart.KubernetesIntermediate17 minProK8S-1207CrashLoopBackOff debugging misses the real stack traceA rollout hits CrashLoopBackOff and on-call engineers keep tailing logs from the current container only.KubernetesIntermediate17 minProK8S-1222Init container completes but the app still crashesAn init container creates generated config successfully and the app still starts without it.KubernetesIntermediate17 minProK8S-1204kubectl logs shows the symptom but not the causeA restart loop looks mysterious because current logs contain only probe or wrapper noise. The evidence that matters is in the previous instance that operators never inspected.KubernetesIntermediate17 minProK8S-1218Readiness remains false foreverA deployment copied a probe path from an older chart revision where an init step created the endpoint first.KubernetesIntermediate17 minProK8S-1191Init container failsA public manifest pattern was updated to simplify ConfigMap structure. The init container still expects the old key and the pod now dies before app startup.KubernetesIntermediate18 minProK8S-1211Readiness never stabilizesA service keeps flapping during boot and the team only increases delay seconds.KubernetesIntermediate18 minProK8S-1225Startup probe keeps failingA workload with a proxy sidecar fails startup probes even though the application container itself is healthy.KubernetesIntermediate18 minProK8S-1230The init container waits forever for DNSA pod design assumes later-stage network policy or sidecar setup before the init step has even finished.KubernetesIntermediate18 minProK8S-1197CrashLoopBackOff is caused by a startup script reading a secret mount path that moved after a Helm refactorThe app container restarts endlessly because a startup script still references the old secret mount location even though the chart now projects the secret elsewhere.KubernetesIntermediate19 minProK8S-1202CrashLoopBackOff looks like app failure but the init script exitsA startup pattern from community posts assumes a mounted file is ready immediately. On first boot, the script reads an empty value and exits before the app can start.KubernetesIntermediate19 minPro