The Secondary Scheduler Operator for Red Hat OpenShift allows you to deploy a custom secondary scheduler in your OKD 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.
Issued: 26 November 2024
The following advisory is available for the Secondary Scheduler Operator for Red Hat OpenShift 1.1.4:
This release of the Secondary Scheduler Operator addresses Common Vulnerabilities and Exposures (CVEs).
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)
Issued: 26 October 2023
The following advisory is available for the Secondary Scheduler Operator for Red Hat OpenShift 1.1.3:
This release of the Secondary Scheduler Operator addresses Common Vulnerabilities and Exposures (CVEs).
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)
Issued: 23 August 2023
The following advisory is available for the Secondary Scheduler Operator for Red Hat OpenShift 1.1.2:
This release of the Secondary Scheduler Operator addresses several Common Vulnerabilities and Exposures (CVEs).
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)
Issued: 1 September 2022
The following advisory is available for the Secondary Scheduler Operator for Red Hat OpenShift 1.1.0:
The Secondary Scheduler Operator security context configuration has been updated to comply with pod security admission enforcement.
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. (BZ#2071684)