Operators can potentially support multiple architectures and operating systems by using manifest lists, which point to the relevant image per arch / os. Investigate if and how we want to support this for our operators. If we do, don't forget to update relevant annotations.

This email triggered this epic: https://lists.corp.redhat.com/archives/operatorframework-pm/2022-April/000071.html

Not sure if this needs doc, and how to do QE (can we get non amd64 linux clusters for tests?)

Konflux

Konflux supports 4 architectures: amd64, arm64, ppc64le, and s390x. We should consider adding support for multiple architecture builds when building the operator image and a single-arch build for the bundle.

ATM, we are supporting linux/x86_64 (x86). Which platforms are relevant?

• Customer (CNV) seems to be interested in arm64 support https://redhat-internal.slack.com/archives/CR8HZL4P3/p1742377266088899 
• Patner (IBM System Z and Power) seems to be interested in ppc64le and s390x support https://docs.google.com/document/d/1uW8F8E_o-3NweFx0knMOuj8GWGf40H9NfSYjWEUEDEY/edit?tab=t.0

Konflux Future Considerations:

• Operator and Operand image should be built with docker-build-multi-platform-oci-ta pipeline, and the PipelineRun files should have the build-platforms value of  linux/x86_64  linux/arm54,  linux/ppc64le and linux/s390x so we would have an image for each architecture.
• Bundle image image should be built with single-arch (linux/x86_64) image since it is a Metadata, and not a Binary. So it will result in one image but with many annotations of supported arch (e.g., operatorframework.io/arch.amd64: supported, operatorframework.io/arch.arm64: supported, operatorframework.io/arch.ppc64le: supported, and operatorframework.io/arch.s390x: supported)

For more see

• https://konflux.pages.redhat.com/docs/users/getting-started/multi-platform-builds.html 
• https://github.com/konflux-ci/olm-operator-konflux-sample/blob/e0fe58178ff82586cfd004065d0586f016aa6a9a/docs/konflux-onboarding.md#customize-tekton-pipleines