Pod Lifecycle Phases
What you'll learn: You'll understand the five distinct phases a Pod moves through from the moment it's created until it terminates.
The Pod's Journey Through States
When you create a Pod in Kubernetes, it doesn't instantly appear running. Like a package moving through a delivery system, your Pod transitions through well-defined phases that reflect its current state in the cluster.
The Five Lifecycle Phases
Pending
The Pod has been accepted by the Kubernetes cluster, but one or more containers aren't ready yet. This includes time spent waiting for the scheduler to assign the Pod to a node, or time needed to pull container images from a registry.
Running
The Pod has been bound to a node, and all containers have been created. At least one container is still running, or is in the process of starting or restarting.
Succeeded
All containers in the Pod have terminated successfully and will not be restarted. This typically happens with batch jobs or one-time tasks that complete their work and exit cleanly.
Failed
All containers in the Pod have terminated, and at least one container has terminated with a failure (non-zero exit code or was terminated by the system).
Unknown
The state of the Pod cannot be determined, usually because of communication errors with the node where the Pod should be running.
Observing Phases
You can check a Pod's current phase using kubectl get pods or kubectl describe pod <pod-name>. The phase appears in the STATUS column or the detailed output.
Key Takeaway: Pods progress through five lifecycle phases—Pending, Running, Succeeded, Failed, and Unknown—each representing a distinct state that helps you understand what's happening with your workloads and troubleshoot issues effectively.