×

The Secondary Scheduler Operator for Red Hat OpenShift allows you to deploy a custom secondary scheduler in your OpenShift Container Platform cluster.

These release notes track the development of the Secondary Scheduler Operator for Red Hat OpenShift.

For more information, see About the Secondary Scheduler Operator.

Release notes for Secondary Scheduler Operator for Red Hat OpenShift 1.2.2

Issued: 18 November 2024

The following advisory is available for the Secondary Scheduler Operator for Red Hat OpenShift 1.2.2:

Bug fixes

  • This release of the Secondary Scheduler Operator addresses several Common Vulnerabilities and Exposures (CVEs).

Known issues

  • Currently, you cannot deploy additional resources, such as config maps, CRDs, or RBAC policies through the Secondary Scheduler Operator. Any resources other than roles and role bindings that are required by your custom secondary scheduler must be applied externally. (WRKLDS-645)

Release notes for Secondary Scheduler Operator for Red Hat OpenShift 1.2.1

Issued: 2024-03-06

The following advisory is available for the Secondary Scheduler Operator for Red Hat OpenShift 1.2.1:

New features and enhancements

Resource limits removed to support large clusters

With this release, resource limits were removed to allow you to use the Secondary Scheduler Operator for large clusters with many nodes and pods without failing due to out-of-memory errors.

Bug fixes

  • This release of the Secondary Scheduler Operator addresses several Common Vulnerabilities and Exposures (CVEs).

Known issues

  • Currently, you cannot deploy additional resources, such as config maps, CRDs, or RBAC policies through the Secondary Scheduler Operator. Any resources other than roles and role bindings that are required by your custom secondary scheduler must be applied externally. (WRKLDS-645)

Release notes for Secondary Scheduler Operator for Red Hat OpenShift 1.2.0

Issued: 1 November 2023

The following advisory is available for the Secondary Scheduler Operator for Red Hat OpenShift 1.2.0:

Bug fixes

  • This release of the Secondary Scheduler Operator addresses several Common Vulnerabilities and Exposures (CVEs).

Known issues

  • Currently, you cannot deploy additional resources, such as config maps, CRDs, or RBAC policies through the Secondary Scheduler Operator. Any resources other than roles and role bindings that are required by your custom secondary scheduler must be applied externally. (WRKLDS-645)