kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Improve the BackoffLimitPerIndex docs

pull/50461/head
Michal Wozniak 2025-04-11 12:24:03 +02:00
parent 598c25992c
commit 7883cba788
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/en/docs/concepts/workloads/controllers/job.md
View File

@ -360,8 +360,14 @@ with `phase: "Succeeded"`.
There are situations where you want to fail a Job after some amount of retries There are situations where you want to fail a Job after some amount of retries
due to a logical error in configuration etc. due to a logical error in configuration etc.
To do so, set `.spec.backoffLimit` to specify the number of retries before 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.
Pods associated with the Job are recreated by the Job controller with an
The `.spec.backoffLimit` is set by default to 6, unless the
[backoff limit per index](#backoff-limit-per-index) (only Indexed Job) is specified.
When `.spec.backoffLimitPerIndex` is specified, then `.spec.backoffLimit` defaults
to 2147483647 (MaxInt32).
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. exponential back-off delay (10s, 20s, 40s ...) capped at six minutes.
The number of retries is calculated in two ways: The number of retries is calculated in two ways: