updatecli VS helm-controller

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

If you're using helm I believe the helm controller could help you here

I agree with Helm Operator, though it is in maintenance mode and on the cusp of replacement with a newer tool. I'm working with FluxCD org now, on the next generation of Helm Operator, check out Helm Controller, under the new Flux2 which is rapidly approaching 100% feature parity (in the sense of approaching a limit, it is for almost all use cases 100% feature parity already) with the stable Flux v1 + Helm Operator.