When defining a
Job, you can define its maximum duration by setting
activeDeadlineSeconds field. It is specified in seconds and is not
set by default. When not set, there is no maximum duration enforced.
The maximum duration is counted from the time when a first pod gets scheduled in
the system, and defines how long a job can be active. It tracks overall time of
an execution and is irrelevant to the number of completions (number of pod replicas
needed to execute a task). After reaching the specified timeout, the job is
terminated by OKD.
The following example shows the part of a
activeDeadlineSeconds field for 30 minutes: