×

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.1.1

Issued: 1 July 2024

The following advisory is available for the Run Once Duration Override Operator 1.1.1: RHSA-2024:1616

New features and enhancements

  • You can install and use the Run Once Duration Override Operator in an OpenShift Container Platform cluster running in FIPS mode.

    To enable FIPS mode for your cluster, you must run the installation program from a Red Hat Enterprise Linux (RHEL) computer configured to operate in FIPS mode. For more information about configuring FIPS mode on RHEL, see Switching RHEL to FIPS mode.

    When running Red Hat Enterprise Linux (RHEL) or Red Hat Enterprise Linux CoreOS (RHCOS) booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the x86_64, ppc64le, and s390x architectures.

Bug fixes

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

Run Once Duration Override Operator 1.1.0

Issued: 28 February 2024

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

Bug fixes

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