Skip to content
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

Unable to connect to tiller on AKS from within cluster #459

Closed
tirumaraiselvan opened this issue Jun 21, 2018 · 6 comments
Closed

Unable to connect to tiller on AKS from within cluster #459

tirumaraiselvan opened this issue Jun 21, 2018 · 6 comments

Comments

@tirumaraiselvan
Copy link

I develop Gitkube (https://github.com/hasura/gitkube). Gitkube is a tool that builds apps INSIDE the cluster and deploys it. It supports installing helm charts.

I am seeing an issue on AKS which does not happen on GKE.

On GKE, everything is fine. When I do helm version from inside the gitkubed pod, I get expected results

Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

On AKS though the story is different. helm version does not resolve tiller.

Output of helm version (note that this is run from inside a pod on the cluster):

$ helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Stuck finding server version

Output of kubectl version:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.7", GitCommit:"b30876a5539f09684ff9fde266fda10b37738c9c", GitTreeState:"clean", BuildDate:"2018-01-16T21:59:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.6", GitCommit:"9f8ebd171479bec0ada837d7ee641dec2f8c6dd1", GitTreeState:"clean", BuildDate:"2018-03-21T15:13:31Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):

AKS v1.9.6

@tirumaraiselvan
Copy link
Author

I should mention, when I try helm upgrade on a chart I get:

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

@tirumaraiselvan
Copy link
Author

From kubernetes/helm:

It seems helm does a port forward with tiller for communication:

kubectl -n kube-system port-forward my-tiller-pod 44134:44134

This throws the same error:

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

Is it a firewall issue with the pod network?

@Flask
Copy link

Flask commented Jun 21, 2018

Probably a duplicate of #434

@rite2nikhil
Copy link

All (in all regions) new cluster creates should be patched with the fix. thanks for your patience, please report if you still see issues. Existing clusters will eventually get patched.

@tirumaraiselvan
Copy link
Author

Yes it works now. Thanks!

@anilsaini1212
Copy link

facing issue while connecting the tiller in EKS ...
helm version --debug
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Error: forwarding ports: error upgrading connection: Upgrade request required

@ghost ghost locked as resolved and limited conversation to collaborators Aug 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants