allow concurrency about helm-tiller HOT 8 CLOSED

closing this one, as Helm v3 does not have such issues

from helm-tiller.

I would recommend to run concurrent helm tiller run -- helm ... commands in docker containers, as making it in the plugin is out of the scope.

from helm-tiller.

Does that address my reported issue about concurrency? Are you suggesting multiple spun up docker containers executing commands concurrently is possible without conflicts? Then I can suggest the author of helmfile @mumoshu to do just that.

from helm-tiller.

if you don't do multiple releases from at the same time for the same helm release, everything will be fine

from helm-tiller.

great...that means concurrency is possible...why not from the plugin? why is that out of scope?

from helm-tiller.

as you need to run helm + pluggin per container

from helm-tiller.

Isn't it because helm tiller run -- helm ... always uses a constant port for running tiller? If each helm tiller run would run tiller on a random port, then this problem would be solved I think. I can't even run helm tiller start-ci && helmfile apply in one window and helm tiller run -- helm status my-app in another window because the helm tiller run kills the start-ci server as well at the time of exit.

from helm-tiller.

as I mentioned before to get to concurrency run helm+tiller in the container.

Helm v3 is under way (very well back compatible with v2) and beta is already available that will make this plugin obsolete soon.

from helm-tiller.