openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS#16936: CQA for secondary scheduler docs

Browse Source
This commit is contained in:
Andrea Hoffer
2026-01-07 14:42:44 -05:00
committed by openshift-cherrypick-robot
parent 8bf87a07c3
commit 455e3314ad
11 changed files with 73 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
nodes/scheduling/secondary_scheduler/index.adoc
View File

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
[role="_abstract"]
You can install the {secondary-scheduler-operator} to run a custom secondary scheduler alongside the default scheduler to schedule pods.
// About the {secondary-scheduler-operator}

1
nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-configuring.adoc
View File

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
[role="_abstract"]
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.
// Installing the {secondary-scheduler-operator}

31
nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.adoc
View File

@@ -6,33 +6,12 @@ include::_attributes/common-attributes.adoc[]
toc::[]
The {secondary-scheduler-operator-full} allows you to deploy a custom secondary scheduler in your {product-title} cluster.
[role="_abstract"]
Review the {secondary-scheduler-operator-full} release notes to track its development and learn what is new and changed with each release.
These release notes track the development of the {secondary-scheduler-operator-full}.
The {secondary-scheduler-operator} allows you to deploy a custom secondary scheduler in your {product-title} cluster.
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.5.0_{context}"]
== Release notes for {secondary-scheduler-operator-full} 1.5.0
Issued: 29 October 2025
The following advisory is available for the {secondary-scheduler-operator-full} 1.5.0:
* link:https://access.redhat.com/errata/RHBA-2025:19251[RHBA-2025:19251]
[id="secondary-scheduler-1.5.0-new-features_{context}"]
=== New features and enhancements
* This release of the {secondary-scheduler-operator} updates the Kubernetes version to 1.33.
// No bug fixes or CVEs to list
// [id="secondary-scheduler-1.5.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.5.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*])
// Release notes for Secondary Scheduler Operator for Red Hat OpenShift 1.5.0
include::modules/nodes-secondary-scheduler-rn-1.5.0.adoc[leveloffset=+1]

3
nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-uninstalling.adoc
View File

@@ -6,7 +6,8 @@ include::_attributes/common-attributes.adoc[]
toc::[]
You can remove the {secondary-scheduler-operator-full} from {product-title} by uninstalling the Operator and removing its related resources.
[role="_abstract"]
If you no longer need the {secondary-scheduler-operator-full} in your cluster, you can uninstall the Operator and remove its related resources.
// Uninstalling the {secondary-scheduler-operator}
include::modules/nodes-secondary-scheduler-uninstall-console.adoc[leveloffset=+1]