Skip to content

Commit 8a2f871

Browse files
authored
Merge pull request #62979 from bergerhoffer/OSDOCS-7182
OSDOCS 7182: Removing unsupported OSSO versions and adding note about…
2 parents a56ec31 + 1549ff3 commit 8a2f871

File tree

5 files changed

+21
-54
lines changed

5 files changed

+21
-54
lines changed

nodes/scheduling/secondary_scheduler/index.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,5 +8,8 @@ toc::[]
88

99
You can install the {secondary-scheduler-operator} to run a custom secondary scheduler alongside the default scheduler to schedule pods.
1010

11+
:operator-name: The {secondary-scheduler-operator}
12+
include::snippets/operator-not-available.adoc[]
13+
1114
// About the {secondary-scheduler-operator}
1215
include::modules/nodes-secondary-scheduler-about.adoc[leveloffset=+1]

nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-configuring.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ include::_attributes/common-attributes.adoc[]
66

77
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.
88

9+
:operator-name: The {secondary-scheduler-operator}
10+
include::snippets/operator-not-available.adoc[]
11+
912
toc::[]
1013

1114
// Installing the {secondary-scheduler-operator}

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

Lines changed: 3 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -10,58 +10,7 @@ The {secondary-scheduler-operator-full} allows you to deploy a custom secondary
1010

1111
These release notes track the development of the {secondary-scheduler-operator-full}.
1212

13-
For more information, see xref:../../../nodes/scheduling/secondary_scheduler/index.adoc#nodes-secondary-scheduler-about_nodes-secondary-scheduler-about[About the {secondary-scheduler-operator}].
14-
15-
[id="secondary-scheduler-operator-release-notes-1.1.1"]
16-
== Release notes for {secondary-scheduler-operator-full} 1.1.1
17-
18-
Issued: 2023-5-18
19-
20-
The following advisory is available for the {secondary-scheduler-operator-full} 1.1.1:
21-
22-
* link:https://access.redhat.com/errata/RHSA-2023:0584[RHSA-2023:0584]
23-
24-
////
25-
// No enhancements in this release
26-
[id="secondary-scheduler-operator-1.1.1-new-features-and-enhancements"]
27-
=== New features and enhancements
28-
29-
* None
30-
////
31-
32-
[id="secondary-scheduler-1.1.1-bug-fixes"]
33-
=== Bug fixes
34-
35-
* This release of the {secondary-scheduler-operator} addresses several Common Vulnerabilities and Exposures (CVEs).
36-
37-
[id="secondary-scheduler-operator-1.1.1-known-issues"]
38-
=== Known issues
39-
40-
* 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*])
13+
:operator-name: The {secondary-scheduler-operator}
14+
include::snippets/operator-not-available.adoc[]
4115

42-
[id="secondary-scheduler-operator-release-notes-1.1.0"]
43-
== Release notes for {secondary-scheduler-operator-full} 1.1.0
44-
45-
Issued: 2022-9-1
46-
47-
The following advisory is available for the {secondary-scheduler-operator-full} 1.1.0:
48-
49-
* link:https://access.redhat.com/errata/RHSA-2022:6152[RHSA-2022:6152]
50-
51-
[id="secondary-scheduler-operator-1.1.0-new-features-and-enhancements"]
52-
=== New features and enhancements
53-
54-
* 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].
55-
56-
////
57-
// No bug fixes in this release
58-
[id="secondary-scheduler-1.1.0-bug-fixes"]
59-
=== Bug fixes
60-
61-
* None
62-
////
63-
64-
[id="secondary-scheduler-operator-1.1.0-known-issues"]
65-
=== Known issues
66-
67-
* 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*])
16+
For more information, see xref:../../../nodes/scheduling/secondary_scheduler/index.adoc#nodes-secondary-scheduler-about_nodes-secondary-scheduler-about[About the {secondary-scheduler-operator}].

nodes/scheduling/secondary_scheduler/nodes-secondary-scheduler-uninstalling.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,9 @@ toc::[]
88

99
You can remove the {secondary-scheduler-operator-full} from {product-title} by uninstalling the Operator and removing its related resources.
1010

11+
:operator-name: The {secondary-scheduler-operator}
12+
include::snippets/operator-not-available.adoc[]
13+
1114
// Uninstalling the {secondary-scheduler-operator}
1215
include::modules/nodes-secondary-scheduler-uninstall-console.adoc[leveloffset=+1]
1316

snippets/operator-not-available.adoc

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
// When including this file, ensure that {operator-name} is set immediately before
2+
// the include. Otherwise it will result in an incorrect replacement.
3+
4+
[IMPORTANT]
5+
====
6+
{operator-name} is not currently available for {product-title} {product-version}. The Operator is planned to be released in the near future.
7+
====
8+
// Undefine {operator-name} attribute, so that any mistakes are easily spotted
9+
:!operator-name:

0 commit comments

Comments
 (0)