updatecli VS kubernetes-management

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

Kind of, the reason why it's a bit difficult to describe the project is because the different component mean different things to different people.

I built updatecli so I could use it to help me maintain infrastructure as code, then bit by bit, I discovered how other people were using it to solve challenges that I didn't imagine.

Scenario 1: https://github.com/jenkins-infra/kubernetes-management/blob/...

We monitor the latest Certmanager chart version available and we bump our git repository so Helmfile can pick the latest version and update our Kubernetes clusters.

If you are looking for real k8s production experience, you could participate to an open infrastructure project. the Jenkins infrastructure is one of them which mean we try to be as open as open possible in meeting, in doc,and almost every git repository are public. You can start review pull request from https://github.com/jenkins-infra/charts and we automate many many more :) otherwise you could also participate in other open infrastructure project such as the Wikipedia one. Disclaimer: I am the lead infra of the Jenkins infrastructure project so feel free to dm me if you want more information.

For Helm, they are different ways to automate helm chart releases depending on the tooling you have access to. On the Jenkins project, we use a command-line tool named updatecli that I build to help us automate file content like for Docker, Puppet, Helm, Yaml and then run it from a Jenkinsfile, it doesn't update Changelog yet.