Skip to content
Permalink
Browse files

Update pod-lifecycle.md (#9593)

Merging these two paragraphs, which both describe the fields included in the PodConditions. The first one mentions 6 fields, but only defines 3 of them. The second one defines two of the remaining three. The missing 6th element ("reason") has been added. Now we have the full list in one single section. Easier to understand.
  • Loading branch information...
apsureda authored and k8s-ci-robot committed Jul 20, 2018
1 parent 83f9560 commit 9a62e82ce9574e838a573f30ddeb60cb0bf96fb6
Showing with 16 additions and 16 deletions.
  1. +16 −16 content/en/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -55,23 +55,23 @@ array has six possible fields:

* The `message` field is a human-readable message indicating details
about the transition.

* The `reason` field is a unique, one-word, CamelCase reason for the condition's last transition.

* The `status` field is a string, with possible values "`True`", "`False`", and "`Unknown`".

* The `type` field is a string with the following possible values:

* `PodScheduled`: the Pod has been scheduled to a node;
* `Ready`: the Pod is able to serve requests and should be added to the load
balancing pools of all matching Services;
* `Initialized`: all [init containers](/docs/concepts/workloads/pods/init-containers)
have started successfully;
* `Unschedulable`: the scheduler cannot schedule the Pod right now, for example
due to lacking of resources or other constraints;
* `ContainersReady`: all containers in the Pod are ready.


A Pod has a PodStatus, which has an array of
[PodConditions](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podcondition-v1-core). Each element
of the PodCondition array has a `type` field and a `status` field. The `type`
field is a string with the following possible values:

* `PodScheduled`: the Pod has been scheduled to a node;
* `Ready`: the Pod is able to serve requests and should be added to the load
balancing pools of all matching Services;
* `Initialized`: all [init containers](/docs/concepts/workloads/pods/init-containers)
have started successfully;
* `Unschedulable`: the scheduler cannot schedule the Pod right now, for example
due to lacking of resources or other constraints;
* `ContainersReady`: all containers in the Pod are ready.

The `status` field is a string, with possible values "`True`", "`False`", and
"`Unknown`".

## Container probes

0 comments on commit 9a62e82

Please sign in to comment.
You can’t perform that action at this time.