installing RabbitMQ on ARM

[4ndr4s]

Describe the bug

while trying to install RabbitMQ on ARM, one of the containers is not running since is pointing to an image that does not have ARM version.

exec /manager: exec format error

To Reproduce

Steps to reproduce the behavior:

1. create a kustomization.yaml with below content:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
 - https://github.com/rabbitmq/cluster-operator.git/config/installation?ref=v2.15.0
 - https://github.com/rabbitmq/messaging-topology-operator.git/config/rbac?ref=v1.17.2
 - https://github.com/rabbitmq/messaging-topology-operator.git/config/default/overlays/cert-manager?ref=v1.17.2

2. kubectl apply using above file.

Expected behavior
Pod running on ARM architecture

Screenshots

With above code a X86 image is deployed, since is pointing to https://github.com/rabbitmq/messaging-topology-operator/blob/main/config/default/base/kustomization.yaml#L18
which using an old image updated more than 2 years ago https://hub.docker.com/r/rabbitmqoperator/messaging-topology-operator-dev/tags

Version and environment information

• Messaging Topology Operator: latest and previous versions
• RabbitMQ: latest
• RabbitMQ Cluster Operator: latest
• Kubernetes: 1.32.0
• Cloud provider or hardware configuration: AWS

Additional context

I believe the code needs to be updated to point to https://hub.docker.com/r/rabbitmqoperator/messaging-topology-operator instead of https://hub.docker.com/r/rabbitmqoperator/messaging-topology-operator-dev/tags

[MirahImage]

Feel free to open a PR with a fix

[4ndr4s]

great, thanks

[Zerpet]

Both operators provide a multi-arch image, you can review that here: https://hub.docker.com/r/rabbitmqoperator/messaging-topology-operator/tags

We never intended for others to consume our kustomize files. The fact that we still use kustomize is due to my lack of time to migrate everything to YTT. I recommend that you consume our regular manifest files, available in the github releases: https://github.com/rabbitmq/messaging-topology-operator/releases

If you are very determined to use our kustomize files, I will recommend to read our Makefile, to understand how we render the manifests with different images: https://github.com/rabbitmq/messaging-topology-operator/blob/main/Makefile#L236-L244

[4ndr4s]

thanks @Zerpet, yes i was aware that the operator is multi-arch but the image used in that kustomization.yaml file is and old one.

Are those kustomize files going to disappear at some point ?

Using rabbitmq kustomize files made simple for us to use RabbitMQ, regarding rendering the files, I patched to use the latest image as workaround, I’ll take a look to the regular manifest files.

not sure if the PR is still relevant, I can send it if need it.

[Zerpet]

Are those kustomize files going to disappear at some point ?

That's my wish, but it's not decided. In other words, I haven't run the idea with everyone in the team. It sits probably in the last place of priority items, so you can assume that those files won't disappear any time soon.

I patched to use the latest image as workaround

I think that's the best solution. The value in that file is a placeholder. We replace it in-place in pretty much every Make target (ugh).

I don't think there's any need to send a PR, although I appreciate the offering and initiative.