×

Cluster administrators can use the Run Once Duration Override 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 Duration Override Operator to run-once pods, you must enable it on each applicable namespace.

These release notes track the development of the Run Once Duration Override Operator for OpenShift Container Platform.

For an overview of the Run Once Duration Override Operator, see About the Run Once Duration Override Operator.

Run Once Duration Override Operator 1.0.2

Issued: 26 November 2024

The following advisory is available for the Run Once Duration Override Operator 1.0.2:

Bug fixes

  • This release of the Run Once Duration Override Operator addresses several Common Vulnerabilities and Exposures (CVEs).

Run Once Duration Override Operator 1.0.1

Issued: 26 October 2023

The following advisory is available for the Run Once Duration Override Operator 1.0.1:

Bug fixes

  • This release of the Run Once Duration Override Operator addresses several Common Vulnerabilities and Exposures (CVEs).

Run Once Duration Override Operator 1.0.0

Issued: 18 May 2023

The following advisory is available for the Run Once Duration Override Operator 1.0.0:

New features and enhancements