From 0f854ec7600b3a4a68663ab13404d3f5ba78e966 Mon Sep 17 00:00:00 2001 From: Leon Barrett Date: Sat, 11 Jul 2020 10:45:07 -0700 Subject: [PATCH] Update content/en/docs/concepts/workloads/controllers/job.md Co-authored-by: Tim Bannister --- content/en/docs/concepts/workloads/controllers/job.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/job.md b/content/en/docs/concepts/workloads/controllers/job.md index 8f6a8c11fe..21e8aceb64 100644 --- a/content/en/docs/concepts/workloads/controllers/job.md +++ b/content/en/docs/concepts/workloads/controllers/job.md @@ -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 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 count is reset when a job pod is deleted or successful without any -other pods failing around that time. +back-off count is reset when a Job's Pod is deleted or successful without any +other Pods for the Job failing around that time. {{< note >}} 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} 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`. -