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

Release notes for MTO 1.0.1 GA

Browse Source
This commit is contained in:
srir
2025-03-10 16:56:13 +05:30
committed by openshift-cherrypick-robot
parent d2191b3eac
commit 34e76c3a29
1 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -12,13 +12,29 @@ These release notes track the development of the Multiarch Tuning Operator.
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].
[id="multi-arch-tuning-operator-release-notes-1-1-0_{context}"]
== Release notes for the Multiarch Tuning Operator 1.1.0
[id="multi-arch-tuning-operator-release-notes-1.0.0_{context}"]
Issued: 18 March 2024
[id="multi-arch-tuning-operator-1-1-0-new-features-and-enhancements_{context}"]
=== New features and enhancements
* The Multiarch Tuning Operator is now supported on managed offerings, including ROSA with Hosted Control Planes (HCP) and other HCP environments.
* 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.
[id="multi-arch-tuning-operator-1-1-0-bug-fixes_{context}"]
==== Bug fixes
* 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*])
[id="multi-arch-tuning-operator-release-notes-1-0-0_{context}"]
== Release notes for the Multiarch Tuning Operator 1.0.0
Issued: 31 October 2024
[id="multi-arch-tuning-operator-1.0.0-new-features-and-enhancements_{context}"]
[id="multi-arch-tuning-operator-1-0-0-new-features-and-enhancements_{context}"]
=== New features and enhancements
* With this release, the Multiarch Tuning Operator supports custom network scenarios and cluster-wide custom registries configurations.