Pod lifecycle
The lifecycle of a Pod is an aggregate of several components, as a Pod has a number of moving parts that can be in a variety of states as it operates. The representation of the lifecycle is how Kubernetes manages running your code for you, in conjunction with the control and feedback loops that work from the various controllers.
The states of a Pod's lifecycle are:
- Pending: The Pod has been created through the API, and is in the process of being scheduled, loaded, and run on one of the Nodes
- Running: The Pod is fully operational and the software is running within the cluster
- Succeeded (or) Failed: The Pod has finished operation (normally or crashed)
- There is a fourth state: Unknown, which is a fairly rare occurrence and is typically only seen when there’s a problem internal to Kubernetes where it doesn’t know the current state of containers, or is unable to communicate with its underlying systems to determine that state
If you are working with long-running code in Containers, then...