Operator/Helm/Localdev Image Sync

[Sharpz7]

We should ensure that all our different methods of working with Armada are using the same release cycle and are up-to-date.

This would involve:

• Running Localdev: https://armadaproject.io/developer
• Running the Helm Deployment: https://armadaproject.io/production-install
• Running the Operator: https://github.com/armadaproject/armada-operator

And ensuring they are in sync with their configs / images. It would also involve checking the other repos in https://github.com/armadaproject and ensuring they are correct too.

This is a great way to get some experience with Armada and understand how it works. Note that you probably need a pretty beefy machine to run it.

┆Issue is synchronized with this Jira Task by Unito

[MeenuyD]

I would like to work on this issue can you guide me on how to get started with this to solve the issue

[Sharpz7]

Hey @MeenuyD. I left links for where you need to begin. Basically, make sure you can run armada, and then you are checking the docker images. Are they all coming from the same place, or not.

We want to use the docker images being built in our CI - so check there for the gold standard

[richscott]

@Sharpz7 We should note that Helm-based deployments of Armada are not supported now.