Skip to content

Commit 84f355f

Browse files
authored
Merge pull request #46227 from bergerhoffer/OSDOCS-3704
OSDOCS-3704: Adding release notes for secondary scheduler operator 1.0.1
2 parents c68a38f + 57643f3 commit 84f355f

File tree

1 file changed

+29
-0
lines changed

1 file changed

+29
-0
lines changed

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

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,35 @@ These release notes track the development of the {secondary-scheduler-operator-f
1212

1313
For more information, see xref:../../../nodes/scheduling/secondary_scheduler/index.adoc#nodes-secondary-scheduler-about_nodes-secondary-scheduler-about[About the {secondary-scheduler-operator}].
1414

15+
[id="secondary-scheduler-operator-release-notes-1.0.1"]
16+
== Release notes for {secondary-scheduler-operator-full} 1.0.1
17+
18+
Issued: 2022-07-28
19+
20+
The following advisory is available for the {secondary-scheduler-operator-full} 1.0.1:
21+
22+
* link:https://access.redhat.com/errata/RHSA-2022:5699[RHSA-2022:5699]
23+
24+
[IMPORTANT]
25+
====
26+
If you are using {secondary-scheduler-operator-full} 1.0.0, it is expected to be automatically upgraded to version 1.0.1 when you update to the next minor release of {product-title}.
27+
====
28+
29+
[id="secondary-scheduler-operator-1.0.1-new-features-and-enhancements"]
30+
=== New features and enhancements
31+
32+
* The maximum {product-title} version for {secondary-scheduler-operator-full} 1.0.1 is 4.11.
33+
34+
[id="secondary-scheduler-1.0.1-bug-fixes"]
35+
=== Bug fixes
36+
37+
* 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*])
38+
39+
[id="secondary-scheduler-operator-1.0.1-known-issues"]
40+
=== Known issues
41+
42+
* 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*])
43+
1544
[id="secondary-scheduler-operator-release-notes-1.0.0"]
1645
== Release notes for {secondary-scheduler-operator-full} 1.0.0
1746

0 commit comments

Comments
 (0)