whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revert "fix max container back off cap (#8979)" (#9074)

Browse Source 
This reverts commit 8f04c2e1ae.
This commit is contained in:
Maciej Szulik
2018-06-15 21:57:28 +02:00
committed by k8s-ci-robot
parent b5e3452661
commit f630a57c1c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
+1 -1
View File
@@ -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 five minutes. The
exponential back-off delay (10s, 20s, 40s ...) capped at six minutes. The
back-off count is reset if no new failed Pods appear before the Job's next
status check.