K3s: Changes to helm chart values or values.yaml aren't always triggering an upgrade
As the title says
cjellick
All 5 comments
Verified by modifying /var/lib/rancher/k3s/server/manifests/traefik.yaml to add spec.valuesContent, on change the helm-install-traefik pod was re-run to process the modification.
erikwilson
on 9 Mar 2019
Is it correct that helm is installed alongside of k3s? I couldn't find it, last time I checked I needed to manually install it.
jwillmer
on 26 Jul 2019
@jwillmer k3s includes a HelmChart CRD that uses https://github.com/rancher/klipper-helm to run helm install/upgrade/remove. There is no tiller pod in the cluster.
@erikwilson I'm seeing similar behavior (upgrades not happening). I've been applying and modifying HelmChart resources directly via kubectl apply, not via the manifests directory. Should I expect that to work?
pmahoney
on 16 Aug 2019
Helm upgrade are broken at the moment, we probably need to remove the old job first.
erikwilson
on 16 Aug 2019
It indeed works fine if the old job is removed manually before applying the updated helm chart. Tested with k3s version v0.7.0.
kubectl delete job --namespace=kube-system helm-install-cert-manager
kubectl apply -f cert-manager-helmchart.yaml
A new install job was properly created.
jmbe
on 18 Aug 2019
Related issues
VictorRobellini
路
3Comments
seanmalloy
路
3Comments
gilkotton
路
3Comments
e-nikolov
路
3Comments
giminni
路
3Comments
Most helpful comment
It indeed works fine if the old job is removed manually before applying the updated helm chart. Tested with k3s version v0.7.0.
A new install job was properly created.