Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to helm chart values or values.yaml aren't always triggering an upgrade #187

Closed
cjellick opened this Issue Mar 8, 2019 · 1 comment

Comments

2 participants
@cjellick
Copy link
Member

cjellick commented Mar 8, 2019

As the title says

see #183

@cjellick cjellick added this to the v0.2.0 milestone Mar 8, 2019

@cjellick cjellick added this to Backlog in K3S Development via automation Mar 8, 2019

@cjellick cjellick added the kind/bug label Mar 8, 2019

@erikwilson

This comment has been minimized.

Copy link
Member

erikwilson commented Mar 9, 2019

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 erikwilson closed this Mar 9, 2019

K3S Development automation moved this from Backlog to Done Mar 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.