✦ For everyone, free.

Practical knowledge for real and everyday life

Home

1.11 Kubernetes Pod Phase Definition

Kubernetes Pod Phase Definition explains the lifecycle states of pods, essential for managing and troubleshooting containerized applications in a Kubernetes environment.

Kubernetes Pod Phase Definition is the precise characterization of the phase field within a Pod's status, defined as a coarse, single-value summary drawn from a fixed set of possible values that describes where a Pod currently stands in its overall lifecycle, distinct from the more granular conditions and container states that accompany it.


Phase as a Coarse Summary

A Single Value from a Fixed Set

A Pod's phase is defined as exactly one value chosen from a fixed enumeration: Pending, Running, Succeeded, Failed, or Unknown, and at any given moment a Pod occupies exactly one of these values, never more than one and never a value outside this set.

Deliberately Low Resolution

The phase field is defined to be deliberately coarse; it is not intended to capture every nuance of a Pod's health, which is why more granular information is tracked separately through conditions and per-container states rather than through additional phase values.

phase { Pending, Running, Succeeded, Failed, Unknown }

Defining Each Phase Value

Pending

Pending is defined as the phase a Pod occupies after being accepted by the cluster but before all of its containers have been created and started, which may include time spent waiting to be scheduled or waiting for container images to be pulled.

Running

Running is defined as the phase in which the Pod has been bound to a node and at least one of its containers is either running, starting, or restarting; this definition specifically does not require that every container be healthy, only that the Pod has progressed past the Pending phase.

Succeeded and Failed

Succeeded and Failed are defined as terminal phases reached once every container in the Pod has terminated, distinguished by whether termination occurred through successful completion or through failure, and once in either terminal phase, a Pod does not transition back to Pending or Running.

Unknown

Unknown is defined as the phase reported when the state of the Pod cannot be determined, typically because communication with the node hosting it has been lost, rather than reflecting any particular state of the containers themselves.


What Phase Deliberately Excludes

Not a Readiness Signal

Phase is explicitly not defined to indicate whether a Pod is ready to serve traffic; a Pod can be in the Running phase while still failing its readiness checks, since readiness is tracked as a separate condition rather than folded into the phase value.

Not Reversible Once Terminal

Once a Pod's phase reaches Succeeded or Failed, its definition does not allow it to revert to an earlier phase; a Pod that needs to run again is defined as a new Pod, not a transition of the existing one.


Pod Phase Progression Diagram

Pending Running Succeeded / Failed