Red Hat Multiarch Tuning 1.4.1 changes what OpenShift teams must check before a downgrade
The operator now accepts namespace-level pod placement configs without a plugins field, but older resource definitions still require it.
Red Hat released Multiarch Tuning Operator 1.4.1 on November 21 with a change to the schema for namespace-scoped PodPlacementConfig resources. The spec.plugins field is now optional. That gives OpenShift teams one less field to specify, but it also creates a difference between rolling back the operator binary and restoring an older custom resource definition (CRD), according to Red Hat’s release advisory.
What changed
Omitting spec.plugins does not turn on any plugins. Red Hat says configurations that already omit the field remain valid after an upgrade. The release also moves the operator’s event reporting to the Kubernetes events.k8s.io/v1 API and ships examples for ClusterPodPlacementConfig, PodPlacementConfig, and ENoExecEvent in the operator bundle. A separate fix addresses a monitoring discovery problem: a transient API failure no longer leaves the operator unable to discover ServiceMonitor and PrometheusRule resources for the rest of the process’s lifetime.
Who should check their rollback plan
The operator is available through the Red Hat Operators catalog in OpenShift Container Platform. Red Hat describes it as a tool for managing workloads in mixed-architecture clusters and in single-architecture clusters moving to a mixed setup. The schema change concerns the namespace-scoped resource; the advisory does not announce the same change for ClusterPodPlacementConfig.
What to do before restoring an older CRD
Check whether the rollback procedure restores a CRD or just rolls back the operator binary. Red Hat says the caveat applies to the CRD, not a binary-only rollback. The CRDs shipped in versions 1.3.0 through 1.3.4 and 1.4.0 are among those that still require spec.plugins. Before reapplying one of those definitions, set spec.plugins to an empty object ({}) on every PodPlacementConfig that omits it, as the advisory directs. Resources without the field do not meet the older schema. The practical change is to check the stored resources before restoring the definition, rather than treating the downgrade as just an operator version change.
sources
- Red Hat Product Enhancement Advisory RHEA-2026:100843access.redhat.com
comments · 0