diff --git a/nodes/scheduling/secondary_scheduler/index.adoc b/nodes/scheduling/secondary_scheduler/index.adoc index d8c70a90d36b..db48a388669c 100644 --- a/nodes/scheduling/secondary_scheduler/index.adoc +++ b/nodes/scheduling/secondary_scheduler/index.adoc @@ -8,5 +8,8 @@ toc::[] You can install the {secondary-scheduler-operator} to run a custom secondary scheduler alongside the default scheduler to schedule pods. +:operator-name: The {secondary-scheduler-operator} +include::snippets/operator-not-available.adoc[] + // About the {secondary-scheduler-operator} include::modules/nodes-secondary-scheduler-about.adoc[leveloffset=+1] diff --git a/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-configuring.adoc b/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-configuring.adoc index 8b45be93c358..957490165cb3 100644 --- a/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-configuring.adoc +++ b/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-configuring.adoc @@ -8,6 +8,9 @@ toc::[] You can run a custom secondary scheduler in {product-title} by installing the {secondary-scheduler-operator}, deploying the secondary scheduler, and setting the secondary scheduler in the pod definition. +:operator-name: The {secondary-scheduler-operator} +include::snippets/operator-not-available.adoc[] + // Installing the {secondary-scheduler-operator} include::modules/nodes-secondary-scheduler-install-console.adoc[leveloffset=+1] diff --git a/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.adoc b/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.adoc index deecbc508b72..f5bfbc895971 100644 --- a/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.adoc +++ b/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.adoc @@ -10,53 +10,7 @@ The {secondary-scheduler-operator-full} allows you to deploy a custom secondary These release notes track the development of the {secondary-scheduler-operator-full}. -For more information, see xref:../../../nodes/scheduling/secondary_scheduler/index.adoc#nodes-secondary-scheduler-about_nodes-secondary-scheduler-about[About the {secondary-scheduler-operator}]. - -[id="secondary-scheduler-operator-release-notes-1.4.1_{context}"] -== Release notes for {secondary-scheduler-operator-full} 1.4.1 - -Issued: 9 July 2025 - -The following advisory is available for the {secondary-scheduler-operator-full} 1.4.1: - -* link:https://access.redhat.com/errata/RHBA-2025:10723[RHBA-2025:10723] - -[id="secondary-scheduler-1.4.1-new-features_{context}"] -=== New features and enhancements - -* This release of the {secondary-scheduler-operator} updates the Kubernetes version to 1.32. - -[id="secondary-scheduler-1.4.1-bug-fixes_{context}"] -=== Bug fixes - -* This release of the {secondary-scheduler-operator} addresses several Common Vulnerabilities and Exposures (CVEs). -* Previously, some secondary scheduler plugins could not be deployed if they needed to create temporary files. This was due to more restricted permissions that were introduced in a previous release. With this update, secondary schedulers deployed through the Operator can create temporary files again and these secondary scheduler plugins can now be deployed successfully. (link:https://issues.redhat.com/browse/OCPBUGS-58154[*OCPBUGS-58154*]) - -[id="secondary-scheduler-operator-1.4.1-known-issues_{context}"] -=== 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. (link:https://issues.redhat.com/browse/WRKLDS-645[*WRKLDS-645*]) +:operator-name: The {secondary-scheduler-operator} +include::snippets/operator-not-available.adoc[] -[id="secondary-scheduler-operator-release-notes-1.4.0_{context}"] -== Release notes for {secondary-scheduler-operator-full} 1.4.0 - -Issued: 6 May 2025 - -The following advisory is available for the {secondary-scheduler-operator-full} 1.4.0: - -* link:https://access.redhat.com/errata/RHBA-2025:4332[RHBA-2025:4332] - -[id="secondary-scheduler-1.4.0-new-features_{context}"] -=== New features and enhancements - -* This release of the {secondary-scheduler-operator} updates the Kubernetes version to 1.31. - -[id="secondary-scheduler-1.4.0-bug-fixes_{context}"] -=== Bug fixes - -* This release of the {secondary-scheduler-operator} addresses several Common Vulnerabilities and Exposures (CVEs). - -[id="secondary-scheduler-operator-1.4.0-known-issues_{context}"] -=== 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. (link:https://issues.redhat.com/browse/WRKLDS-645[*WRKLDS-645*]) +For more information, see xref:../../../nodes/scheduling/secondary_scheduler/index.adoc#nodes-secondary-scheduler-about_nodes-secondary-scheduler-about[About the {secondary-scheduler-operator}]. diff --git a/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-uninstalling.adoc b/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-uninstalling.adoc index 6f8929ad7e07..d42e48e49ca4 100644 --- a/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-uninstalling.adoc +++ b/nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-uninstalling.adoc @@ -8,6 +8,9 @@ toc::[] You can remove the {secondary-scheduler-operator-full} from {product-title} by uninstalling the Operator and removing its related resources. +:operator-name: The {secondary-scheduler-operator} +include::snippets/operator-not-available.adoc[] + // Uninstalling the {secondary-scheduler-operator} include::modules/nodes-secondary-scheduler-uninstall-console.adoc[leveloffset=+1]