From 9a62e82ce9574e838a573f30ddeb60cb0bf96fb6 Mon Sep 17 00:00:00 2001 From: Alfonso Palacios Date: Sat, 21 Jul 2018 00:58:46 +0200 Subject: [PATCH] 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. --- .../concepts/workloads/pods/pod-lifecycle.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index b94d7a595d..ed9af77d0e 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/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. -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: +* 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. -* `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