Permalink
Browse files

clarify Job behaviour once active deadline seconds is exceeded (#11745)

  • Loading branch information...
Joseph-Irving authored and k8s-ci-robot committed Dec 17, 2018
1 parent 6202a63 commit 7f9e1d59fc126072b6c65b67051454e72b20b80b
Showing with 1 addition and 2 deletions.
  1. +1 −2 content/en/docs/concepts/workloads/controllers/jobs-run-to-completion.md
@@ -221,8 +221,7 @@ By default, a Job will run uninterrupted unless a Pod fails, at which point the
Do this by setting the `.spec.activeDeadlineSeconds` field of the Job to a number of seconds.

The `activeDeadlineSeconds` applies to the duration of the job, no matter how many Pods are created.
Once a Job reaches `activeDeadlineSeconds`, the Job and all of its Pods are terminated.
The result is that the job has a status with `reason: DeadlineExceeded`.
Once a Job reaches `activeDeadlineSeconds`, all of its Pods are terminated and the Job status will become `type: Failed` with `reason: DeadlineExceeded`.

Note that a Job's `.spec.activeDeadlineSeconds` takes precedence over its `.spec.backoffLimit`. Therefore, a Job that is retrying one or more failed Pods will not deploy additional Pods once it reaches the time limit specified by `activeDeadlineSeconds`, even if the `backoffLimit` is not yet reached.

0 comments on commit 7f9e1d5

Please sign in to comment.