From e5639400134e4b88cac14fe6f24d4dbd97016cf1 Mon Sep 17 00:00:00 2001 From: lopes22 Date: Mon, 3 Aug 2020 21:11:55 -0400 Subject: [PATCH 1/2] Update pod-lifecycle.md --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 2b292d376d..2e856570be 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -124,7 +124,7 @@ about when the container entered the `Running` state. ### `Terminated` {#container-state-terminated} -A container in the `Terminated` state has begin execution and has then either run to +A container in the `Terminated` state had began execution and then has either run to completion or has failed for some reason. When you use `kubectl` to query a Pod with a container that is `Terminated`, you see a reason, and exit code, and the start and finish time for that container's period of execution. From bf37bf0498c4c3fc09fa12770d0d0afafcfb2c08 Mon Sep 17 00:00:00 2001 From: Zach Corleissen Date: Tue, 18 Aug 2020 14:15:30 -0700 Subject: [PATCH 2/2] Update content/en/docs/concepts/workloads/pods/pod-lifecycle.md --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 2e856570be..4cbf3c2670 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -124,9 +124,9 @@ about when the container entered the `Running` state. ### `Terminated` {#container-state-terminated} -A container in the `Terminated` state had began execution and then has either run to -completion or has failed for some reason. When you use `kubectl` to query a Pod with -a container that is `Terminated`, you see a reason, and exit code, and the start and +A container in the `Terminated` state began execution and then either ran to +completion or failed for some reason. When you use `kubectl` to query a Pod with +a container that is `Terminated`, you see a reason, an exit code, and the start and finish time for that container's period of execution. If a container has a `preStop` hook configured, that runs before the container enters @@ -442,4 +442,3 @@ This avoids a resource leak as Pods are created and terminated over time. * For detailed information about Pod / Container status in the API, see [PodStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podstatus-v1-core) and [ContainerStatus](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#containerstatus-v1-core). -