From 403bb200d9acf89784272f7fce276f520378ca86 Mon Sep 17 00:00:00 2001 From: Bin Liu Date: Fri, 1 Jun 2018 06:28:56 +0800 Subject: [PATCH] Add parameter name to document to understand (#8523) --- content/en/docs/concepts/workloads/pods/pod-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index 59ddd17dbc..98125e3758 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -159,7 +159,7 @@ once bound to a node, a Pod will never be rebound to another node. 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 the master) will expire and be automatically destroyed. +duration (determined by `terminated-pod-gc-threshold` in the master) will expire and be automatically destroyed. Three types of controllers are available: