[caasp-beta] Helm transport is closing

Nikhil Manchanda nikhil at manchanda.me
Wed Nov 22 14:52:07 MST 2017

Hello vinicius:

Can you go into more detail as to what you are trying to deploy? Sending us
a copy of the tiller logs will also be helpful.

That said, I have most often seen that error in the case where your chart
is trying to deploy an ELB resource, which is timing out. For CaaSP, we do
not support ELB, so if this is the case -- then the error is expected. You
will need to update your chart (or your values.yaml) to pick a different
way of accessing your service (something like NodePort would work, or
ingress if you happen to have an ingress controller deployed.)

Hope this helps,


On Wed, Nov 22, 2017 at 4:34 AM, vinicius <vneuhauss at suse.com> wrote:

> Hello All.
> I'm trying to do a deploy from a application using helm . I'm using helm
> client 2.6.1 same of tiller server. But when I try to do the deploy I have
> this output:
> E1122 10:28:50.743105   20036 portforward.go:178] lost connection to pod
> Error: transport is closing
> _______________________________________________
> caasp-beta mailing list
> caasp-beta at lists.suse.com
> http://lists.suse.com/mailman/listinfo/caasp-beta
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20171122/71e4cec7/attachment.htm>

More information about the caasp-beta mailing list