Helm chart version needs to be incremented along with app version #794

Closed
opened 2024-03-30 13:58:59 +00:00 by kurtraschke · 1 comment

I am using Flux to deploy Garage in a local Kubernetes cluster with the Helm chart. I noticed that Flux was not deploying new versions of Garage as they were released, and found that this was due to the Helm chart's version number not changing with new releases.

It appears that when the Garage version number is incremented for a new release (as in 8670140358, for example), the appVersion parameter in Chart.yaml is updated, but not the version parameter. As the Helm documentation and the note in Chart.yaml describe, the version parameter also needs to be updated when the appVersion parameter is updated.

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 0.4.1
I am using [Flux](https://fluxcd.io/) to deploy Garage in a local Kubernetes cluster with the [Helm chart](https://git.deuxfleurs.fr/Deuxfleurs/garage/src/commit/8670140358353542b0c92b7b72a1d223ea2fe068/script/helm). I noticed that Flux was not deploying new versions of Garage as they were released, and found that this was due to the Helm chart's version number not changing with new releases. It appears that when the Garage version number is incremented for a new release (as in 8670140358353542b0c92b7b72a1d223ea2fe068, for example), the `appVersion` parameter in `Chart.yaml` is updated, but not the `version` parameter. As the Helm documentation and the note in `Chart.yaml` describe, the `version` parameter also needs to be updated when the `appVersion` parameter is updated. ``` # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) version: 0.4.1 ```
Owner

Thanks, noted.

Thanks, noted.
lx closed this issue 2024-04-08 16:01:28 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#794
No description provided.