-
Notifications
You must be signed in to change notification settings - Fork 564
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
helmfile destroy fails, needs concurrency flag #690
Comments
@Morriz Hey! Mind sharing the error message you saw? |
Yeah, this is what I get (not revealing anything):
|
I don't see what is going wrong in the tiller-plugin on that line 114 or 128 |
Yeah, it seems the plugin tries to stop the local tiller but others processes are using it of course. |
so please add |
@Morriz Ah, that seems like the current restriction of the helm-tiller integration #449 Tiller needs two or three ports to bind, grpc, metrics, and optionally trace ports. The error seems to be due to that grpc and metrics ports are conflicting across tiller instances. So yes, the shortterm solution would be to add |
tnx....it would be nicer if the plugin would allow for concurrency...I will create a request for that |
I would love to, but where can I find the master binary? |
Just grab the latest binary from github releases. |
0.77 works great now...mega tnx for the quick update! |
Glad to help! Thanks for your confirmation |
A global
helmfile destroy
gives errors for some charts. If I destroy them one after the other withhelmfile -l name=$release destroy
I see no errors.I suspect something is conflicting because of the attempted concurrency, and therefor I would like the destroy command to also honour
--concurrency=1
.The text was updated successfully, but these errors were encountered: