Fix pod-lifecycle typo bescheduled.
Replace bescheduled by be scheduled.
This commit is contained in:
parent
6ce337253e
commit
6622de0b5e
|
|
@ -78,7 +78,7 @@ Here are the possible values for `phase`:
|
||||||
|
|
||||||
Value | Description
|
Value | Description
|
||||||
:-----|:-----------
|
:-----|:-----------
|
||||||
`Pending` | The Pod has been accepted by the Kubernetes cluster, but one or more of the containers has not been set up and made ready to run. This includes time a Pod spends waiting to bescheduled as well as the time spent downloading container images over the network.
|
`Pending` | The Pod has been accepted by the Kubernetes cluster, but one or more of the containers has not been set up and made ready to run. This includes time a Pod spends waiting to be scheduled as well as the time spent downloading container images over the network.
|
||||||
`Running` | The Pod has been bound to a node, and all of the containers have been created. At least one container is still running, or is in the process of starting or restarting.
|
`Running` | The Pod has been bound to a node, and all of the 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 in success, and will not be restarted.
|
`Succeeded` | All containers in the Pod have terminated in success, and will not be restarted.
|
||||||
`Failed` | All containers in the Pod have terminated, and at least one container has terminated in failure. That is, the container either exited with non-zero status or was terminated by the system.
|
`Failed` | All containers in the Pod have terminated, and at least one container has terminated in failure. That is, the container either exited with non-zero status or was terminated by the system.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue