-
Notifications
You must be signed in to change notification settings - Fork 32
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
Detect failed deployments and notify or force #48
Comments
It's hard to decide what to do here because helm has its hands tied. If you Maybe removing the release's storage (ConfigMap/Secret) from the tiller namespace could work in most cases as long as you're not messing with CRD's? In general, the 2.7.1+ behavior is borked and really needs a proper fix in helm. |
at least we could modify the error message. Instead of |
I think a flag that allow helm to take over existing resources and override them(without deleting them or leading to any kind of down time) will be very useful in such cases(provide a descent bypass, other claim that force delete and create - hence potential downtime). |
Helm 3 actually has this capability by adding the correct labels to resources.
Agreed, it would be nice if this bug were better handled by Helm. Helm 3 is getting better at it, but it's still not perfect. |
There is a known helm issue: helm/helm#3208 where as sometimes a failed release causes the install to fail. An easy work around exist with
helm delete --purge <FAILED RELEASE
thenhelm upgrade --install
or justhelm upgrade --install --force
. Reckoner should detect this issue and either notify the user or force the install.The text was updated successfully, but these errors were encountered: