diff --git a/assets/images/running-a-pod.png b/assets/images/running-a-pod.png
new file mode 100644
index 0000000..3b35867
Binary files /dev/null and b/assets/images/running-a-pod.png differ
diff --git a/assets/images/terminate-pod.jpg b/assets/images/terminate-pod.jpg
new file mode 100644
index 0000000..92cdb8c
Binary files /dev/null and b/assets/images/terminate-pod.jpg differ
diff --git a/categories/devops/kubernetes.md b/categories/devops/kubernetes.md
index b0d88b1..c84ae92 100644
--- a/categories/devops/kubernetes.md
+++ b/categories/devops/kubernetes.md
@@ -163,7 +163,6 @@ Through its lifecycle, a Pod can attain following states:
 
 - `Pending`: The pod is accepted by the Kubernetes system but its container(s) is/are not created yet.
 
-
 - `Running`: The pod is scheduled on a node and all its containers are created and at-least one container is in Running state.
 
 - `Succeeded`: All container(s) in the Pod have exited with status 0 and will not be restarted.
@@ -172,6 +171,19 @@ Through its lifecycle, a Pod can attain following states:
 
 - `CrashLoopBackoff`: The container fails to start and is tried again and again.
 
+
+### Flow chart of running a pod
+
+![running a pod](https://raw.githubusercontent.com/wahyd4/knowledge-mind-mapping/master/assets/images/running-a-pod.png)
+
+Chart from: <https://blog.heptio.com/core-kubernetes-jazz-improv-over-orchestration-a7903ea92ca>
+
+## Kubernetes termination lifecycle
+
+![termination lifecycle](https://raw.githubusercontent.com/wahyd4/knowledge-mind-mapping/master/assets/images/terminate-pod.jpg)
+
+Chart from: <https://dzone.com/articles/kubernetes-lifecycle-of-a-pod>
+
 ## Zero down time deployment
 
 Set strategy type to `RollingUpdate` instead of `Recreate`