Skip to content

Pod phase states

Pod phase states represent the high-level status of a Pod's lifecycle within the Kubernetes cluster. These phases are strictly defined and serve as the primary indicator for the current state of a Pod, often used as the first point of reference during troubleshooting.^[400-devops-06-kubernetes-k8s-ithelp-day10-readme.md]

When viewing Pods using kubectl get pods, these phases appear in the STATUS column.^[400-devops-06-kubernetes-k8s-ithelp-day10-readme.md]

Defined States

There are five possible values for a Pod's phase:

  • Pending: The Pod has been accepted by the cluster, but the scheduler has not yet assigned it to a node, or container images are still being downloaded.^[400-devops-06-kubernetes-k8s-ithelp-day10-readme.md]
  • 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.^[400-devops-06-kubernetes-k8s-ithelp-day10-readme.md]
  • Succeeded: All containers in the Pod have terminated successfully and will not be restarted.^[400-devops-06-kubernetes-k8s-ithelp-day10-readme.md]
  • Failed: All containers in the Pod have terminated, and at least one terminated in failure (e.g., exited with a non-zero status code or was terminated by the system).^[400-devops-06-kubernetes-k8s-ithelp-day10-readme.md]
  • Unknown: The state of the Pod cannot be obtained, typically due to a communication error between the master node and the node where the Pod resides.^[400-devops-06-kubernetes-k8s-ithelp-day10-readme.md]

Sources

^[400-devops-06-kubernetes-k8s-ithelp-day10-readme.md]