openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 03:47:04 +01:00
Code Issues Releases Activity

OSDOCS-17797 adding unsupported snippet to RODOO

Browse Source
This commit is contained in:
cbippley
2026-01-27 15:52:48 -05:00
parent 22648ebd3b
commit 33ec5a4b4a
4 changed files with 14 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
nodes/pods/run_once_duration_override/index.adoc
View File

@@ -6,7 +6,11 @@ include::_attributes/common-attributes.adoc[]
toc::[]
[role="_abstract"]
You can use the {run-once-operator} to specify a maximum time limit that run-once pods can be active for.
:operator-name: The {run-once-operator}
include::snippets/operator-not-available.adoc[]
// About the {run-once-operator}
include::modules/rodoo-about.adoc[leveloffset=+1]

4
nodes/pods/run_once_duration_override/run-once-duration-override-install.adoc
View File

@@ -6,8 +6,12 @@ include::_attributes/common-attributes.adoc[]
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.

14
nodes/pods/run_once_duration_override/run-once-duration-override-release-notes.adoc
View File

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
[role="_abstract"]
Cluster administrators can use the {run-once-operator} to force a limit on the time that run-once pods can be active. After the time limit expires, the cluster tries to terminate the run-once pods. The main reason to have such a limit is to prevent tasks such as builds to run for an excessive amount of time.
To apply the run-once duration override from the {run-once-operator} to run-once pods, you must enable it on each applicable namespace.
@@ -14,14 +15,5 @@ These release notes track the development of the {run-once-operator} for {produc
For an overview of the {run-once-operator}, see xref:../../../nodes/pods/run_once_duration_override/index.adoc#run-once-about_run-once-duration-override-about[About the {run-once-operator}].
[id="run-once-duration-override-operator-release-notes-1-3-0_{context}"]
== {run-once-operator} 1.3.0
Issued: 9 July 2025
The following advisory is available for the {run-once-operator} 1.3.0: (link:https://access.redhat.com/errata/RHBA-2025:10725[RHBA-2025-10725])
[id="run-once-duration-override-operator-1-3-0-bug-fixes_{context}"]
=== Bug fixes
* This release of the {run-once-operator} addresses several Common Vulnerabilities and Exposures (CVEs).
:operator-name: The {run-once-operator}
include::snippets/operator-not-available.adoc[]

3
nodes/pods/run_once_duration_override/run-once-duration-override-uninstall.adoc
View File

@@ -8,6 +8,9 @@ toc::[]
You can remove the {run-once-operator} from {product-title} by uninstalling the Operator and removing its related resources.
:operator-name: The {run-once-operator}
include::snippets/operator-not-available.adoc[]
// Uninstalling the {run-once-operator}
include::modules/rodoo-uninstall-operator.adoc[leveloffset=+1]