Updated jobs-run-to-completion.md (#8379)

pull/8409/merge
kbatuigas 2018-05-17 15:37:53 -07:00 committed by k8s-ci-robot
parent 052e528e6f
commit c285768c66
1 changed files with 2 additions and 2 deletions

View File

@ -192,8 +192,8 @@ 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
back-off limit is reset if no new failed Pods appear before the Job's next
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.
{{< note >}}