Secondary Scheduler Operator release notes - Controlling pod placement onto nodes (scheduling) | Nodes

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.

Release notes for Secondary Scheduler Operator for Red Hat OpenShift 1.1.0

Issued: 2022-9-1

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)

Issued: 2022-07-28

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

The maximum OKD version for Secondary Scheduler Operator for Red Hat OpenShift 1.0.1 is 4.11.

Previously, the secondary scheduler deployment was not deleted after the secondary scheduler custom resource (CR) was deleted, which prevented the Secondary Scheduler Operator and operand from being fully uninstalled. The secondary scheduler deployment is now deleted when the secondary scheduler CR is deleted, so that the Secondary Scheduler Operator can now be fully uninstalled. (BZ#2100923)

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)

Issued: 2022-04-18

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

This is the initial release of the Secondary Scheduler Operator for Red Hat OpenShift.

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)