argocd-image-updater VS reliza-cli

Use the ArgoCD image updater

We already have software agents in GitOps ecosystem that modify the state in git. Ie, the image updater in ArgoCD. It watches the docker registry. When it sees a new image, it updates git on a user's behalf.

If you are using ArgoCD you might be able to use this: https://argocd-image-updater.readthedocs.io/en/stable/

I just found this in my travels, I have only gone so far as reading the introduction but seems to be a fit? https://github.com/argoproj-labs/argocd-image-updater

I've used Keel and more recently ArgoCD Image Updater (Using ArgoCD to manage deployments).

https://argocd-image-updater.readthedocs.io/en/stable/ maybe?

Use the image updater

To answer your question you should promote docker images between environments. There are many ways to do this. Check https://argocd-image-updater.readthedocs.io/en/stable/ if you haven't seen it already.

For ArgoCD there’s argocd-image-updated, https://argocd-image-updater.readthedocs.io/en/stable/

We currently provide accurate lead time and deployment frequency calculation capability via Reliza Hub - https://relizahub.com (operating in public preview). Since we track when each piece of code gets deployed to each environment and each instance. Other metrics are on our roadmap.

You then either leverage getlatestrelease functionality of reliza-cli - https://github.com/relizaio/reliza-cli#6-use-case-request-latest-release-per-project-or-product to request approved image or you can use replacetags functionality over your Dockerfile which would replace base image with the one approved - https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment

Note, we have recently released a new replacetags functionality (https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment - going to add tutorial soon) so that you don't need to use templating language inside your helm charts or manifests and instead it would just parse raw base yamls into correct images per each environment.

We're building Reliza Hub for this purpose - https://relizahub.com

Note, it's somewhat outdated and we're working on a new one based on new replacetags functionality - https://github.com/relizaio/reliza-cli#72-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-instance-and-revision