You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The helm controller right now hashes the values and won't ever re-run helm even if a resource originally created by the helm run is missing, ie a service. For context, Flux v2 does this.
I would expect/like to see that if I'm using this controller, that it has additional logic to ensure the result of the helm chart is always applied regardless if valuesContent has changed. This way I can depend on it being the source of truth. As it stands right now, once applied, if someone modifies a resource it created, it won't undo the modifications until the valuesContent or some other element of HelmChart is modified to trigger a helm run.
Since this can be coupled with the k3s auto-deploy manifests, this would be a necessary change to make it really gitops source of truth like model even though we aren't employing the git side of things here.
This is related to a problem/feature with the auto-deploy manifests as well k3s-io/k3s#3711
The text was updated successfully, but these errors were encountered:
The helm controller right now hashes the values and won't ever re-run helm even if a resource originally created by the helm run is missing, ie a service. For context, Flux v2 does this.
I would expect/like to see that if I'm using this controller, that it has additional logic to ensure the result of the helm chart is always applied regardless if valuesContent has changed. This way I can depend on it being the source of truth. As it stands right now, once applied, if someone modifies a resource it created, it won't undo the modifications until the valuesContent or some other element of HelmChart is modified to trigger a helm run.
Since this can be coupled with the k3s auto-deploy manifests, this would be a necessary change to make it really gitops source of truth like model even though we aren't employing the git side of things here.
This is related to a problem/feature with the auto-deploy manifests as well k3s-io/k3s#3711
The text was updated successfully, but these errors were encountered: