Question about helm chart

[GurdipS5]

Hi all,
Basic question so please excuse me.

I am looking to use UpdateCLI for helm charts. Reading the documentation, it sounds like it only updates the version tag (or the different variations of this).

I am a little confused because between versions of Helm charts, there are changes that may deprecate or add parameters in values files, etc.

Thanks

[olblak]

Updatecli can be used either as a declarative approach where you specify your update strategy in a yaml file.
For example, you have various Updatecli configuration located here:

• jenkins-infra/helm-charts
• epinion/helm-charts

That approach allows you to define with great precision where the information is coming from, the required condition, and the files to update.

The other approach is what we call the autodiscovery where Updatecli tries to find and update what it can.
For example this manifest

• epinio/helm-charts
  The autodiscovery looks for docker image tag define like

image:
  image: xxx
  tag: yyy

or

images:
  example:
    image: xxx
    tag: yyy

You can have an idea about what Updatecli can detect by running

updatecli diff ghcr.io/updatecli/policies/autodiscovery/helm
updatecli manifest show ghcr.io/updatecli/policies/autodiscovery/helm

[GurdipS5]

Thanks. I was told that updatecli only updates the helm version tag, but not the rest of the chart. Is this correct?

…

On Wed, Feb 5, 2025 at 4:33 PM Olivier Vernin ***@***.***> wrote: Updatecli can be used either as a declarative approach where you specify your update strategy in a yaml file. For example, you have various Updatecli configuration located here: - jenkins-infra/helm-charts <https://github.com/jenkins-infra/helm-charts/tree/main/updatecli/updatecli.d> - epinion/helm-charts <https://github.com/epinio/helm-charts/blob/main/updatecli/updatecli.d/epinio-ui.yaml> That approach allows you to define with great precision where the information is coming from, the required condition, and the files to update. The other approach is what we call the autodiscovery where Updatecli tries to find and update what it can. For example this manifest - epinio/helm-charts <https://github.com/epinio/helm-charts/blob/main/updatecli/updatecli.d/autodiscovery/default.yaml> The autodiscovery looks for docker image tag define like image: image: xxx tag: yyy or images: example: image: xxx tag: yyy You can have an idea about what Updatecli can detect by running updatecli diff ghcr.io/updatecli/policies/autodiscovery/helm updatecli manifest show ghcr.io/updatecli/policies/autodiscovery/helm — Reply to this email directly, view it on GitHub <#3716 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AU2JXHC5CPAJ5LOY4YVR5QD2OI4PJAVCNFSM6AAAAABWIE5WJWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBXGE4TEMQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[olblak]

Updatecli allows you to update whatever information is in your Helm chart as long as you describe in a yaml file what you want to update. That's what the "declarative" feature is about

You have to decide where the information is coming from, that's the purpose of source plugins.
Then you use a target to specify what file to update. Usually, in the context of Helm chart update, we use either the yaml or the helm chart plugin.

1. YAML: this plugin allows you to specify what a yaml file to monitor for update
2. Helm chart: The helm chart plugin is based on the yaml plugin, but it also handles appversion and automate helm chart version update.