updatecli VS argocd-image-updater

Updatecli is a useful tool for fine-tuning update strategies in DevOps. As you've probably experienced, manual updates often result in outdated specs because figuring out what can be updated is tricky.

A second innovation is the use of updatecli to observe the available application helm releases and update the environment helm charts automatically to promote application versions:

Maybe you could have a look to Updatecli https://github.com/updatecli/updatecli

I built https://github.com/updatecli/updatecli for those situations where it's not possible to guess the next tag version. It's a declarative dependency management tool, You define in a manifest how your Yaml should be update, then run updatecli from your CI to automatically open a PullRequest on your repository when a new container tag is available.

Like in this package https://github.com/updatecli/updatecli/tree/main/pkg/plugins...

And the matching between a package and a resource kind is done here

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/