Kubernetes jobs and back-off limit values: is the value a number of retries or minutes?
No confusion about the .spec.backoffLimit is is the number of retries.
The Job controller recreates the failed Pods (associated with the Job) in an exponential delay (10s, 20s, 40s, ... , 360s). And of course, this delay time is set by the Job controller.
- If the Pod fails, after 10s new Pod will be created
- If fails again, after 20s new one will be created
- If fails again, after 40s new one comes
- If fails again, next one comes after 80s (1m 20s)
- If fails again, next one comes after 160s (2m 40s)
- If fails again, after 320s (5m 20s), new Pod comes
- If fails again, after 360s (not 640s, cause it is greater than 360s or 6m) you will see the next one