Helm chart version needs to be incremented along with app version #794
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#794
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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), theappVersion
parameter inChart.yaml
is updated, but not theversion
parameter. As the Helm documentation and the note inChart.yaml
describe, theversion
parameter also needs to be updated when theappVersion
parameter is updated.Thanks, noted.