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#15350: Removing unsupported OSSO versions for 4.20

Browse Source
This commit is contained in:
Andrea Hoffer
2025-09-10 16:34:36 -04:00
committed by openshift-cherrypick-robot
parent ad20be6814
commit 8d711bcadc
4 changed files with 12 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -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]

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

@@ -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]

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

@@ -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}.
:operator-name: The {secondary-scheduler-operator}
include::snippets/operator-not-available.adoc[]
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*])
[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*])

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

@@ -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]