-
Notifications
You must be signed in to change notification settings - Fork 163
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
[Question] Helm upgrade option for Atomic #615
Comments
Helm Operator has the
There are a few different things that people mean when they say atomic, with respect to Helm. That flag from Helm Operator https://fluxcd.io/flux/components/helm/helmreleases/#configuring-failure-remediation Can you say a bit more about what you were hoping to get from the Atomic option? Is it just a drop-in replacement for the old behavior that you're looking for?
Hope that is what you were looking for! The "atomic" stuff that's discussed in the roadmap is all about whether or not Helm Controller can perform drift detection and reliably revert changes to your Helm release's manifests (output) when someone makes a change inside the cluster. That's a different thing, was never supported in Helm Operator before, but if that's what you are looking for, I hear it might be landing soon (at least in an experimental form!) |
Closing this, as I think @kingdonb has answered your question accordingly. The changes Kingdon is further talking about have landed in the |
Looking at helm-operator there was a possible Atomic option. Is the Atomic option configurable in helm-controller?
The text was updated successfully, but these errors were encountered: