mirror of
https://github.com/wahyd4/knowledge.git
synced 2026-08-08 20:57:48 +10:00
Add kubernetes flow chart
This commit is contained in:
Binary file not shown.
|
After Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 94 KiB |
@@ -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
|
||||
|
||||

|
||||
|
||||
Chart from: <https://blog.heptio.com/core-kubernetes-jazz-improv-over-orchestration-a7903ea92ca>
|
||||
|
||||
## Kubernetes termination lifecycle
|
||||
|
||||

|
||||
|
||||
Chart from: <https://dzone.com/articles/kubernetes-lifecycle-of-a-pod>
|
||||
|
||||
## Zero down time deployment
|
||||
|
||||
Set strategy type to `RollingUpdate` instead of `Recreate`
|
||||
|
||||
Reference in New Issue
Block a user