Merge pull request #22452 from leon-barrett/patch-1

Fix description of back-off count reset
This commit is contained in:
Kubernetes Prow Robot 2020-07-11 11:21:21 -07:00 committed by GitHub
commit 46bf00b75b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions

View File

@ -215,8 +215,8 @@ 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 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 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 six minutes. The
back-off count is reset if no new failed Pods appear before the Job's next back-off count is reset when a Job's Pod is deleted or successful without any
status check. other Pods for the Job failing around that time.
{{< note >}} {{< note >}}
If your job has `restartPolicy = "OnFailure"`, keep in mind that your container running the Job If your job has `restartPolicy = "OnFailure"`, keep in mind that your container running the Job
@ -474,4 +474,3 @@ object, but maintains complete control over what Pods are created and how work i
## Cron Jobs {#cron-jobs} ## Cron Jobs {#cron-jobs}
You can use a [`CronJob`](/docs/concepts/workloads/controllers/cron-jobs/) to create a Job that will run at specified times/dates, similar to the Unix tool `cron`. You can use a [`CronJob`](/docs/concepts/workloads/controllers/cron-jobs/) to create a Job that will run at specified times/dates, similar to the Unix tool `cron`.