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

fix max container back off cap (#8979)

Browse Source 
see https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kubelet.go#L126
This commit is contained in:
Cong Ding
2018-06-11 10:53:31 -07:00
committed by k8s-ci-robot
parent a21554381e
commit 8f04c2e1ae
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 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.