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

Merge pull request #63027 from openshift-cherrypick-robot/cherry-pick-62979-to-enterprise-4.14

Browse Source 
[enterprise-4.14] OSDOCS 7182: Removing unsupported OSSO versions and adding note about…
This commit is contained in:
Andrea Hoffer
2023-08-01 14:35:29 -04:00
committed by GitHub
parent 1a9f85c5ea a0d40b29e2
commit 7842e2f7c2
5 changed files with 21 additions and 54 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

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

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

@@ -10,58 +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.1.1"]
== Release notes for {secondary-scheduler-operator-full} 1.1.1
Issued: 2023-5-18
The following advisory is available for the {secondary-scheduler-operator-full} 1.1.1:
* link:https://access.redhat.com/errata/RHSA-2023:0584[RHSA-2023:0584]
////
// No enhancements in this release
[id="secondary-scheduler-operator-1.1.1-new-features-and-enhancements"]
=== New features and enhancements
* None
////
[id="secondary-scheduler-1.1.1-bug-fixes"]
=== Bug fixes
* This release of the {secondary-scheduler-operator} addresses several Common Vulnerabilities and Exposures (CVEs).
[id="secondary-scheduler-operator-1.1.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://issues.redhat.com/browse/WRKLDS-645[*WRKLDS-645*])
[id="secondary-scheduler-operator-release-notes-1.1.0"]
== Release notes for {secondary-scheduler-operator-full} 1.1.0
Issued: 2022-9-1
The following advisory is available for the {secondary-scheduler-operator-full} 1.1.0:
* link:https://access.redhat.com/errata/RHSA-2022:6152[RHSA-2022:6152]
[id="secondary-scheduler-operator-1.1.0-new-features-and-enhancements"]
=== New features and enhancements
* The {secondary-scheduler-operator} security context configuration has been updated to comply with xref:../../../authentication/understanding-and-managing-pod-security-admission.adoc#understanding-and-managing-pod-security-admission[pod security admission enforcement].
////
// No bug fixes in this release
[id="secondary-scheduler-1.1.0-bug-fixes"]
=== Bug fixes
* None
////
[id="secondary-scheduler-operator-1.1.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*])

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]

9
snippets/operator-not-available.adoc Normal file
View File

@@ -0,0 +1,9 @@
// When including this file, ensure that {operator-name} is set immediately before
// the include. Otherwise it will result in an incorrect replacement.
[IMPORTANT]
====
{operator-name} is not currently available for {product-title} {product-version}. The Operator is planned to be released in the near future.
====
// Undefine {operator-name} attribute, so that any mistakes are easily spotted
:!operator-name: