EC
PodInitializing
KubernetesINFOPod StateHIGH confidence

Init containers are still running

What this means

PodInitializing is a transient pod state indicating that one or more init containers are running but have not yet completed. The main application containers have not started. This is normal during pod startup but becomes a concern if the state persists beyond the expected initialization time.

Why it happens
  1. 1Init containers are running their setup tasks (e.g., database migration, config generation)
  2. 2Init container is waiting for a dependency to become available
  3. 3Init container is performing a time-consuming operation
How to reproduce

Pod shows PodInitializing for longer than expected during a deployment.

trigger — this will error
trigger — this will error
kubectl get pods
# NAME    READY   STATUS            RESTARTS   AGE
# mypod   0/1     PodInitializing   0          2m

kubectl logs mypod -c init-container-name

expected output

NAME    READY   STATUS            RESTARTS   AGE
mypod   0/1     PodInitializing   0          2m

Fix

Monitor init container progress

WHEN PodInitializing persists for longer than expected

Monitor init container progress
# Follow init container logs
kubectl logs mypod -c init-container-name -f

# Check how long the pod has been initializing
kubectl describe pod mypod | grep -E "Start Time|Init Containers"

Why this works

Streaming logs reveals whether the init container is progressing or stuck.

Sources
Official documentation ↗

Kubernetes Documentation

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All Kubernetes errors