Open
Description
What did you do to encounter the bug?
- Followed steps to migrate from MongoDB Community Operator.
- Scaled down old operator.
- Installed mongodb-kubernetes helm chart to ARM64 k8s cluster.
- Operator crashes due to mismatched architecture.
What did you expect?
Operator deploys and functions normally with ARM64 support.
What happened instead?
Operator crashes with exec format error due to mismatched architecture (AMD64).
Operator Information
- Operator 1.0.1
- MongoDB 7.0.20
Kubernetes Cluster Information
- k3s
- 1.32.4
- quay.io
Additional context
The new operator images should be built with ARM64 support. ARM64 users of the MongoDB Community Operator currently not able to migrate.
Other referenced images, such as mongodb-kubernetes-init-appdb, also only have AMD64 image.
Metadata
Metadata
Assignees
Labels
No labels
Activity
vinilage commentedon May 21, 2025
Hi @sholdee, and thanks for bringing up the topic and for providing all the information.
The MongoDB Community Operator, currently part of MCK, does not support ARM architecture.
We are currently discussing to implement this option and I hope soon it will be available.
Thanks and have a great day.
vinilage commentedon May 22, 2025
@sholdee Just to complete my answer: since we don’t currently provide ARM support for MCK and if this is a blocker for you, I recommend using a previous version of the MongoDB Community Operator.
sholdee commentedon May 22, 2025
Hi @vinilage, I have been running the MongoDB Community Operator for a while already, so I will stick with that and keep an eye out for MongoDB Controllers for Kubernetes ARM64 support. Thank you!
vinilage commentedon May 23, 2025
Thanks to you, @sholdee, and happy to hear you've been using our operator for a while.