From 2eac42a8417a1233f55f1c3755e7bafc9fc035fd Mon Sep 17 00:00:00 2001 From: Joseph Irving Date: Fri, 19 Apr 2019 09:09:55 +0100 Subject: [PATCH] remove invalid pod phases (#13840) --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 30ca4db714..9395a7bd18 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -39,9 +39,6 @@ Value | Description `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. `Unknown` | For some reason the state of the Pod could not be obtained, typically due to an error in communicating with the host of the Pod. -`Completed` | The pod has run to completion as there's nothing to keep it running eg. Completed Jobs. -`CrashLoopBackOff` | This means that one of the containers in the pod has exited unexpectedly, and perhaps with a non-zero error code even after restarting due to [restart policy](#restart-policy). - ## Pod conditions