Merge pull request #50107 from bergerhoffer/OSDOCS-4003

OSDOCS-4003: Removing SSO versions that aren't applicable for 4.12

Author: bergerhoffer

nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-release-notes.adoc

@@ -38,54 +38,3 @@ The following advisory is available for the {secondary-scheduler-operator-full}
 === 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://bugzilla.redhat.com/show_bug.cgi?id=2071684[*BZ#2071684*])
-
-[id="secondary-scheduler-operator-release-notes-1.0.1"]
-== Release notes for {secondary-scheduler-operator-full} 1.0.1
-
-Issued: 2022-07-28
-
-The following advisory is available for the {secondary-scheduler-operator-full} 1.0.1:
-
-* link:https://access.redhat.com/errata/RHSA-2022:5699[RHSA-2022:5699]
-
-[id="secondary-scheduler-operator-1.0.1-new-features-and-enhancements"]
-=== New features and enhancements
-
-* The maximum {product-title} version for {secondary-scheduler-operator-full} 1.0.1 is 4.11.
-
-[id="secondary-scheduler-1.0.1-bug-fixes"]
-=== Bug fixes
-
-* 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. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2100923[*BZ#2100923*])
-
-[id="secondary-scheduler-operator-1.0.1-known-issues"]
-=== 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://bugzilla.redhat.com/show_bug.cgi?id=2071684[*BZ#2071684*])
-
-[id="secondary-scheduler-operator-release-notes-1.0.0"]
-== Release notes for {secondary-scheduler-operator-full} 1.0.0
-
-Issued: 2022-04-18
-
-The following advisory is available for the {secondary-scheduler-operator-full} 1.0.0:
-
-* link:https://access.redhat.com/errata/RHEA-2022:1346[RHEA-2022:1346]
-
-[id="secondary-scheduler-operator-1.0.0-new-features-and-enhancements"]
-=== New features and enhancements
-
-* This is the initial release of the {secondary-scheduler-operator-full}.
-
-////
-// No bug fixes in the initial release
-[id="secondary-scheduler-1.0.0-bug-fixes"]
-=== Bug fixes
-
-* None
-////
-
-[id="secondary-scheduler-operator-1.0.0-known-issues"]
-=== 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://bugzilla.redhat.com/show_bug.cgi?id=2071684[*BZ#2071684*])