Skip to content

Commit 354a8b3

Browse files
authored
Merge pull request #90525 from sr1kar99/mto-1-1-0-rn-cp
Release notes for MTO 1.0.1 GA
2 parents 13ea10b + 117ea4b commit 354a8b3

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

post_installation_configuration/configuring-multi-arch-compute-machines/multi-arch-tuning-operator-release-notes.adoc

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,29 @@ These release notes track the development of the Multiarch Tuning Operator.
1212

1313
For more information, see xref:../../post_installation_configuration/configuring-multi-arch-compute-machines/multiarch-tuning-operator.adoc#multiarch-tuning-operator[Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator].
1414

15+
[id="multi-arch-tuning-operator-release-notes-1-1-0_{context}"]
16+
== Release notes for the Multiarch Tuning Operator 1.1.0
1517

16-
[id="multi-arch-tuning-operator-release-notes-1.0.0_{context}"]
18+
Issued: 18 March 2024
19+
20+
[id="multi-arch-tuning-operator-1-1-0-new-features-and-enhancements_{context}"]
21+
=== New features and enhancements
22+
23+
* The Multiarch Tuning Operator is now supported on managed offerings, including ROSA with Hosted Control Planes (HCP) and other HCP environments.
24+
25+
* With this release, you can configure architecture-aware workload scheduling by using the new `plugins` field in the `ClusterPodPlacementConfig` object. You can use the `plugins.nodeAffinityScoring` field to set architecture preferences for pod placement. If you enable the `nodeAffinityScoring` plugin, the scheduler first filters out nodes that do not meet the pod requirements. Then, the scheduler prioritizes the remaining nodes based on the architecture scores defined in the `nodeAffinityScoring.platforms` field.
26+
27+
[id="multi-arch-tuning-operator-1-1-0-bug-fixes_{context}"]
28+
==== Bug fixes
29+
30+
* With this release, the Multiarch Tuning Operator does not update the `nodeAffinity` field for pods that are managed by a daemon set. (link:https://issues.redhat.com/browse/OCPBUGS-45885[*OCPBUGS-45885*])
31+
32+
[id="multi-arch-tuning-operator-release-notes-1-0-0_{context}"]
1733
== Release notes for the Multiarch Tuning Operator 1.0.0
1834

1935
Issued: 31 October 2024
2036

21-
[id="multi-arch-tuning-operator-1.0.0-new-features-and-enhancements_{context}"]
37+
[id="multi-arch-tuning-operator-1-0-0-new-features-and-enhancements_{context}"]
2238
=== New features and enhancements
2339

2440
* With this release, the Multiarch Tuning Operator supports custom network scenarios and cluster-wide custom registries configurations.

0 commit comments

Comments
 (0)