From 8f04c2e1ae1261308da4e662befd7d160999e302 Mon Sep 17 00:00:00 2001 From: Cong Ding Date: Mon, 11 Jun 2018 10:53:31 -0700 Subject: [PATCH] fix max container back off cap (#8979) see https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kubelet.go#L126 --- .../concepts/workloads/controllers/jobs-run-to-completion.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md index 9b9b8ab124..6496bba36b 100644 --- a/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md +++ b/content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md @@ -193,7 +193,7 @@ due to a logical error in configuration etc. To do so, set `.spec.backoffLimit` to specify the number of retries before considering a Job as failed. The back-off limit is set by default to 6. Failed Pods associated with the Job are recreated by the Job controller with an -exponential back-off delay (10s, 20s, 40s ...) capped at six minutes. The +exponential back-off delay (10s, 20s, 40s ...) capped at five minutes. The back-off count is reset if no new failed Pods appear before the Job's next status check.