Skip to content

Commit d86f83b

Browse files
committed
OSDOCS#14952: Release notes for OSSO 1.4.1
1 parent a9b5386 commit d86f83b

File tree

1 file changed

+25
-2
lines changed

1 file changed

+25
-2
lines changed

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

Lines changed: 25 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,31 @@ 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.4.1_{context}"]
16+
== Release notes for {secondary-scheduler-operator-full} 1.4.1
17+
18+
Issued: 9 July 2025
19+
20+
The following advisory is available for the {secondary-scheduler-operator-full} 1.4.1:
21+
22+
* link:https://access.redhat.com/errata/RHBA-2025:10723[RHBA-2025:10723]
23+
24+
[id="secondary-scheduler-1.4.1-new-features_{context}"]
25+
=== New features and enhancements
26+
27+
* This release of the {secondary-scheduler-operator} updates the Kubernetes version to 1.32.
28+
29+
[id="secondary-scheduler-1.4.1-bug-fixes_{context}"]
30+
=== Bug fixes
31+
32+
* This release of the {secondary-scheduler-operator} addresses several Common Vulnerabilities and Exposures (CVEs).
33+
* 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*])
34+
35+
[id="secondary-scheduler-operator-1.4.1-known-issues_{context}"]
36+
=== Known issues
37+
38+
* 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*])
39+
1540
[id="secondary-scheduler-operator-release-notes-1.4.0_{context}"]
1641
== Release notes for {secondary-scheduler-operator-full} 1.4.0
1742

@@ -21,8 +46,6 @@ The following advisory is available for the {secondary-scheduler-operator-full}
2146

2247
* link:https://access.redhat.com/errata/RHBA-2025:4332[RHBA-2025:4332]
2348

24-
// TODO: Update errata link once available
25-
2649
[id="secondary-scheduler-1.4.0-new-features_{context}"]
2750
=== New features and enhancements
2851

0 commit comments

Comments
 (0)