Pod lifecycle states¶

Pod lifecycle states describe the specific phases a Pod goes through from creation to termination within the Kubernetes orchestration system^[400-devops__06-Kubernetes__k8s-paas__原理及源码解析__Kubernetes基本概念.md]. These states are determined by the status of the containers running inside the Pod and the success of scheduling operations^[400-devops__06-Kubernetes__k8s-paas__原理及源码解析__Kubernetes基本概念.md].

Core States¶

The primary phase states include:

• Pending: The Pod's YAML configuration has been accepted and the API object exists in etcd, but the Pod has not yet been scheduled successfully or its containers have not been fully created^[400-devops__06-Kubernetes__k8s-paas__原理及源码解析__Kubernetes基本概念.md].
• Running: The Pod has been successfully bound to a node, all necessary containers have been created, and at least one container is currently in operation^[400-devops__06-Kubernetes__k8s-paas__原理及源码解析__Kubernetes基本概念.md].
• Succeeded: All containers within the Pod have terminated successfully, typically indicating the completion of a one-time task or job^[400-devops__06-Kubernetes__k8s-paas__原理及源码解析__Kubernetes基本概念.md].
• Failed: At least one container in the Pod terminated in an abnormal state (non-zero exit code), usually requiring debugging via Events or logs^[400-devops__06-Kubernetes__k8s-paas__原理及源码解析__Kubernetes基本概念.md].
• Unknown: The system cannot determine the state of the Pod, often due to a communication failure between the kubelet on the node and the kube-apiserver^[400-devops__06-Kubernetes__k8s-paas__原理及源码解析__Kubernetes基本概念.md].

Related Concepts¶

• Kubernetes
• Container orchestration
• Pod

Sources¶

• 400-devops__06-Kubernetes__k8s-paas__原理及源码解析__Kubernetes基本概念.md