helm: Error forwarding ports: error upgrading connection

Hi, from my side I solved the Error: forwarding ports: error upgrading connection: Upgrade request required issue with the following command:

$ export HELM_HOST=":44134"
$ tiller -listen ${HELM_HOST} -alsologtostderr >/dev/null 2>&1 &

Note: The export of the variable is useful too

---

Configuration:

• Kubernetes Client Version: 1.14.1
• Kubernetes Server Version: 1.10.3
• Helm Client Version: 2.12.3
• Helm Server Version: 2.12.3

helm not work when the number nodes of cluster larger than 1,

Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Kubernetes: &version.Info{Major:"1", Minor:"9+", GitVersion:"v1.9.7-gke.3", GitCommit:"9b5b719c5f295c99de68ffb5b63101b0e0175376", GitTreeState:"clean", BuildDate:"2018-05-31T18:32:23Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Hi, from my side I solved the Error: forwarding ports: error upgrading connection: Upgrade request required issue with the following command:

$ export HELM_HOST=":44134"
$ tiller -listen ${HELM_HOST} -alsologtostderr >/dev/null 2>&1 &

Note: The export of the variable is useful too

Configuration:

• Kubernetes Client Version: 1.14.1
• Kubernetes Server Version: 1.10.3
• Helm Client Version: 2.12.3
• Helm Server Version: 2.12.3

Hi, This worked for me. Could you please explain us your solution ?

Not sure if this is related. I am getting this error in AKS but not in GKE. I use helm from within the cluster to make releases.

Error: forwarding ports: error upgrading connection: Upgrade request required

Just to be safe (in case this is unrelated), I created a new issue: https://github.com/kubernetes/helm/issues/4254

@nidhi-ag It starts a local instance of tiller which connects to your remote Kubernetes cluster which works around the error related to failing to connect to the remote instance of tiller. https://helm.sh/docs/install/#running-tiller-locally

@axot if you’re having issues with kubectl port-forward, then that’s gonna be a connection issue on Kubernetes’ end, not on Helm’s 😃 I’d file a ticket with GKE.

@technosophos Any idea how to fix this when using helm inside of a pod in the k8?

I’m using gitlab-runners to build projects inside of pods. Kubectl works, its pointing to https://kubernetes.default but helm doesn’t.

$ docker run --rm ${CONTAINER_TEST_IMAGE} helm ls
Error: Get http://localhost:8080/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp [::1]:8080: getsockopt: connection refused

$ docker run --rm ${CONTAINER_TEST_IMAGE} kubectl cluster-info
Kubernetes master is running at http://localhost:8080