helm: Error: forwarding ports: error upgrading connection: error sending request:
Error: forwarding ports: error upgrading connection: error sending request: Post https://ip:port/
Output of helm version:
Client: &version.Version{SemVer:“v2.13.1”, …
Error: forwarding ports: error upgrading connection: error sending request: Post https://ip:port/api/v1/namespaces/kube-system/pods/<pod-name>/portforward: unexpected EOF
Output of kubectl version:
Client Version: version.Info{Major:“1”, Minor:“12”, GitVersion:“v1.12.7+1.2.3.el7”, GitCommit:“cfc2012a27408ac61c8883084204d10b31fe020c”, GitTreeState:“archive”, BuildDate:“2019-05-23T20:00:05Z”, GoVersion:“go1.10.8”, Compiler:“gc”, Platform:“linux/amd64”}
Server Version: version.Info{Major:“1”, Minor:“9”, GitVersion:“v1.9.1+2.1.5.el7”, GitCommit:“ea4c95b07dd46d5563e4f6851ede13157bf04266”, GitTreeState:“archive”, BuildDate:“2018-03-23T02:54:15Z”, GoVersion:“go1.9.2”, Compiler:“gc”, Platform:“linux/amd64”}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): Linux, Kube
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (7 by maintainers)
Behind the scenes, helm initialized a
kubectl port-forwardto tiller. Can you try establishing a connection to tiller manually usingkubectl port-forward -n kube-system tiller-deploy-78dfcfd45d 44134:44134? Sometimes the cluster hasn’t been properly configured to handle those requests.