-
Notifications
You must be signed in to change notification settings - Fork 1.1k
be able to pass args to helm on upgrades #1621
Comments
The Helm Operator is using the helm go client not the CLI, so passing args is not possible. The apiVersion: flux.weave.works/v1beta1
kind: HelmRelease
metadata:
name: redis
spec:
releaseName: redis
timeout: 600
resetValues: true
chart:
repository: https://kubernetes-charts.storage.googleapis.com/
name: redis
version: 5.1.3
valueFileSecrets:
- name: redis-auth
values:
usePassword: true |
@davidkarlsen This makes sense -- it's a "release the chart with exactly these values" mode. On that basis, I would expect you'd want it to reset every time it runs upgrade? |
I would expect the same result as helm upgrade --install --reset-values - f values.yaml That way the chart version plus the current config in git is the result. Regardless of any history |
Got it 👍 Then yep I think a field in the HelmRelease is a good way to expose this option. |
I’v implemented this in the reset-values branch https://github.com/weaveworks/flux/tree/reset-values I’ll make a PR next year :) |
Using resetValues: false on an existing helm release doesn't works, I've already opened an issue fluxcd/helm-operator#352 |
It would be useful to be able to pass arguments to helm on upgrades (via the helm operator).
Specifically I am looking for
--reset-values
.The reason for this is that I sometimes install initially with some overriding values, but later on want to use the chart-defaults. This is not possible as it is now - if you ever installed with some specific values initially, you cannot fallback to the defaults by removing the overriding values in the
values:
section of the HelmRelease anymore.The text was updated successfully, but these errors were encountered: