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

[feature] valdiate the output of the helm run against the cluster #107

Open
ekristen opened this issue Jul 26, 2021 · 0 comments
Open

[feature] valdiate the output of the helm run against the cluster #107

ekristen opened this issue Jul 26, 2021 · 0 comments

Comments

@ekristen
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant