MULTIARCH#5446: Release notes for MTO 1.1.1

Author: sr1kar99

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

@@ -12,6 +12,22 @@ 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-1_{context}"]
+== Release notes for the Multiarch Tuning Operator 1.1.1
+
+Issued: 27 May 2025
+
+[id="multi-arch-tuning-operator-1-1-z-bug-fixes_{context}"]
+=== Bug fixes
+
+* Previously, the pod placement operand did not support authenticating registries using wildcard entries in the hostname of their pull secret. This caused inconsistent behavior with Kubelet when pulling images, because Kubelet supported wildcard entries while the operand required exact hostname matches. As a result, image pulls could fail unexpectedly when registries used wildcard hostnames.
++
+With this release, the pod placement operand supports pull secrets that include wildcard hostnames, ensuring consistent and reliable image authentication and pulling. 
+
+* Previously, when image inspection failed after all retries and the `nodeAffinityScoring` plugin was enabled, the pod placement operand applied incorrect `nodeAffinityScoring` labels.
++
+With this release, the operand sets `nodeAffinityScoring` labels correctly, even when image inspection fails. It now applies these labels independently of the required affinity process to ensure accurate and consistent scheduling. 
+
 [id="multi-arch-tuning-operator-release-notes-1-1-0_{context}"]
 == Release notes for the Multiarch Tuning Operator 1.1.0