kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

modify terminated-pod-gc-threshold explanation (#15272) (#17183) 

* modify terminated-pod-gc-threshold explanation (#15272)

* modify terminated-pod-gc-threshold explanation (#15272)
pull/17429/head
Jin Hase 2019-11-05 13:52:38 +09:00 committed by Kubernetes Prow Robot
parent 733f376823
commit 6b261c7611
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
content/en/docs/concepts/workloads/pods/pod-lifecycle.md
View File

@ -276,10 +276,11 @@ once bound to a node, a Pod will never be rebound to another node.
## Pod lifetime
In general, Pods do not disappear until someone destroys them. This might be a
human or a controller. The only exception to
this rule is that Pods with a `phase` of Succeeded or Failed for more than some
duration (determined by `terminated-pod-gc-threshold` in the master) will expire and be automatically destroyed.
In general, Pods remain until a human or controller process explicitly removes them.
The control plane cleans up terminated Pods (with a phase of `Succeeded` or
`Failed`), when the number of Pods exceeds the configured threshold
(determined by `terminated-pod-gc-threshold` in the kube-controller-manager).
This avoids a resource leak as Pods are created and terminated over time.
Three types of controllers are available: