From 2e0287dd8636f013bb4e2ee70ed58654164a9276 Mon Sep 17 00:00:00 2001
From: Barnabas Makonda <6409210+MAKOSCAFEE@users.noreply.github.com>
Date: Fri, 1 Feb 2019 01:22:25 +0300
Subject: [PATCH] Added missing pod status in pod lifecycle docs (#12397)

* Added missing pod status in pod lifecycle docs

Added information about `completed` and `CrashLoopBackOff`

* update example of completed status
---
 content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
index b95dcec1ff3e5..38fa995727817 100644
--- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
+++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md
@@ -39,6 +39,9 @@ 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