# Mongo Operator and ARM **URL:** \ **Category:** Percona Operator for MongoDB\ **Created:** [August 9, 2023, 7:00am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326 "2023-08-09T07:00:06Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![sergelog](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@sergelog](https://forums.percona.com/u/sergelog)\ **Post date:** [August 9, 2023, 7:00am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/1 "2023-08-09T07:00:06Z")
## Description: Hello, do you have a plan to build/push mongo operator for ARM64 arch? Thanks. ## Version: psmdb-operator 1.14.0 ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [August 9, 2023, 8:07am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/2 "2023-08-09T08:07:08Z")
Hello @sergelog , we do have this in our roadmap. [https://jira.percona.com/browse/K8SPSMDB-948](https://jira.percona.com/browse/K8SPSMDB-948) > > > \### Community Note > > \* Please vote on this issue by adding a :thumbsup: \[reaction…\](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request > \* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request > \* If you are interested in working on this issue or have submitted a pull request, please leave a comment > > > > \*\*Tell us about the feature\*\* > > We want to deploy mongo operator and mongo replicaset on EKS with ARM EC2 nodes. Please provide multi arch container images  allowing to pull appropriate architecture depending runtime > > \[Link to JIRA\](https://jira.percona.com/browse/K8SPSMDB-948) Can you share more details about your use case? For example, is it about EC2 Graviton on AWS? Or is it more about edge IOT cases? Etc. ---
**Author:** ![sergelog](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@sergelog](https://forums.percona.com/u/sergelog)\ **Post date:** [August 9, 2023, 9:06am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/3 "2023-08-09T09:06:29Z")
The short answer is price. ARM instances are cheaper. I have the app: python (django), postgres, redis, rabbit, mongo. And all components work fine except Mongo. We decided to migrate from bitnami-mongo to Percona. I’ve almost given up with mongo-arm64. But I’ve just noticed, you introduced a mongo-server for arm. Mongo operator was written on golang, and I hope it would not be complicated to release an arm version mongo-operator (Dockerfile has values already). Kubernetes controlplane and other components (addons) support many planform architecture now. So mongo operator like controplate, should follow this idea. Thanks. ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [May 29, 2024, 7:18am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/4 "2024-05-29T07:18:26Z")
@sergelog - we added the support for ARM in Percona Operator for MongoDB 1.16.0: [Percona Operator for MongoDB 1.16.0 (2024-05-24) - Percona Operator for MongoDB](https://docs.percona.com/percona-operator-for-mongodb/RN/Kubernetes-Operator-for-PSMONGODB-RN1.16.0.html) The only caveat - PMM does not support ARM yet. You can deploy the Operator and database with PMM disabled. ---
**Author:** ![sergelog](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@sergelog](https://forums.percona.com/u/sergelog)\ **Post date:** [May 29, 2024, 7:29am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/5 "2024-05-29T07:29:53Z")
Thank you. I’ve tested it already. Do you have a plane to rename image tags like x.x.x-multi to regular tag? Just today Mongo operator during upgrade, replaced the multi-arch image to amd only. Thanks. ---
**Author:** ![Kay\_Khan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kay_khan/32/17023_2.png) [@Kay\_Khan](https://forums.percona.com/u/Kay_Khan)\ **Post date:** [June 25, 2024, 7:39am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/6 "2024-06-25T07:39:32Z")
Hi im trying to get percona MongoDB server running on aws ec2 graviton instances (arm) can you provide your config? curious if you had to anything special to get it working. Im running into an issue (see my latest pos) ---
**Author:** ![sergelog](https://avatars.discourse-cdn.com/v4/letter/s/7feea3/32.png) [@sergelog](https://forums.percona.com/u/sergelog)\ **Post date:** [June 25, 2024, 8:35am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/7 "2024-06-25T08:35:38Z")
Hi, change the images tag to **multi** and disable updateStrategy: [https://hub.docker.com/r/percona/percona-server-mongodb/tags?page=&page\_size=&ordering=&name=multi](https://hub.docker.com/r/percona/percona-server-mongodb/tags?page=&page_size=&ordering=&name=multi) ```yaml image: repository: percona/percona-server-mongodb tag: 6.0.15-12-multi backup: enabled: true image: repository: percona/percona-backup-mongodb tag: 2.4.1-multi ``` ---
**Author:** ![Kay\_Khan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kay_khan/32/17023_2.png) [@Kay\_Khan](https://forums.percona.com/u/Kay_Khan)\ **Post date:** [June 25, 2024, 12:15pm UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/8 "2024-06-25T12:15:31Z")
thank you, but unsure why you need to disable updateStrategy smartupdate? ---
**Author:** ![Tomislav\_Plavcic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/tomislav_plavcic/32/9717_2.png) [@Tomislav\_Plavcic](https://forums.percona.com/u/Tomislav_Plavcic)\ **Post date:** [June 26, 2024, 11:05am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/9 "2024-06-26T11:05:45Z")
Hi @Kay_Khan ! You don’t need to change `updateStrategy: SmartUpdate`, just make sure to set `upgradeOptions.apply: disabled`. This basically disables the automatic upgrades of database cluster (since I think our version service is still not aware of these multi images), but it is still using the SmartUpdate strategy for different config updates which is recommended. ---
**Author:** ![Kay\_Khan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/kay_khan/32/17023_2.png) [@Kay\_Khan](https://forums.percona.com/u/Kay_Khan)\ **Post date:** [June 27, 2024, 8:27am UTC](https://forums.percona.com/t/mongo-operator-and-arm/24326/10 "2024-06-27T08:27:03Z")
thank you for the response