1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/nodes/pods/run_once_duration_override/run-once-duration-override-install.adoc
2026-01-28 14:55:07 -05:00

28 lines
1.1 KiB
Plaintext

:_mod-docs-content-type: ASSEMBLY
[id="run-once-duration-override-install"]
= Overriding the active deadline for run-once pods
include::_attributes/common-attributes.adoc[]
:context: run-once-duration-override-install
toc::[]
[role="_abstract"]
You can use the {run-once-operator} to specify a maximum time limit that run-once pods can be active for. By enabling the run-once duration override on a namespace, all future run-once pods created or updated in that namespace have their `activeDeadlineSeconds` field set to the value specified by the {run-once-operator}.
:operator-name: The {run-once-operator}
include::snippets/operator-not-available.adoc[]
[NOTE]
====
If both the run-once pod and the {run-once-operator} have their `activeDeadlineSeconds` value set, the lower of the two values is used.
====
// Installing the {run-once-operator}
include::modules/rodoo-install-operator.adoc[leveloffset=+1]
// Enabling the run-once duration override on a namespace
include::modules/rodoo-enable-override.adoc[leveloffset=+1]
// Updating the run-once active deadline override value
include::modules/rodoo-update-active-deadline-seconds.adoc[leveloffset=+1]