The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.
The Multiarch Tuning Operator enhances the operational experience within multi-architecture clusters, and single-architecture clusters that are migrating to a multi-architecture compute configuration.
This Operator implements the clusterpodplacementconfigs custom resource (CR) to support architecture-aware workload scheduling.
To enable architecture-aware workload scheduling, you must create the ClusterPodPlacementConfig object. When you create the ClusterPodPlacementConfig object, this Operator deploys an operand.
When a pod is created, the operand performs the following actions:
When the operand removes the scheduling gate, the pod enters the scheduling cycle. The workload is then scheduled on nodes based on the supported architectures.
The operator can be installed in 4.16+ Openshift Clusters from the Red Hat Operators catalog. For more details, see https://docs.openshift.com/container-platform/4.16/post_installation_configuration/configuring-multi-arch-compute-machines/multiarch-tuning-operator.html.
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | Multiarch Tuning Operator |
| Summary | The Multiarch Tuning Operator enhances the user experience for administrators of Openshift clusters with multi-architecture compute nodes or Site Reliability Engineers willing to migrate from single-arch to multi-arch OpenShift |
| Description | The Multiarch Tuning Operator enhances the user experience for administrators of Openshift clusters with multi-architecture compute nodes or Site Reliability Engineers willing to migrate from single-arch to multi-arch OpenShift |
| Provider | Red Hat |
| Repository name | multiarch-tuning/multiarch-tuning-operator-bundle |
| Image version | 1.2.2 |
| Architecture | amd64 |
Use a registry service account token to authenticate your container client. This allows you to pull images without using your personal Red Hat credentials, which is recommended for CI/CD pipelines and automated deployments.
Run the following command, then enter your registry token credentials when prompted by the terminal.
Pull the image
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
Run the following command, then enter your login credentials when prompted by the terminal.
Pull the image
Use the following instructions to get images from a Red Hat container registry without providing authentication.
Use the following command(s) from a system with podman installed.
A source manifest is available for each Red Hat product container image and includes a list of the representative open source packages used in the image. These manifests are publicly available at:
ftp.redhat.com/pub/redhat/containers/To view a list of the open source packages used in a specific container image, choose the namespace, repository, and tag to find the appropriate source manifest.
Example| Namespace | Repository | Tag |
|---|---|---|
| multiarch-tuning/ | multiarch-tuning-operator-bundle | 1.2.2-1770115611.txt |
A listing of every version of source packages used in published container images is publicly available at:
ftp.redhat.com/pub/redhat/containers/src.index.html