proxy does not work

[r-moiseev]

Created cluster in EastUs. kubectl works fine, then i installed helm and helm is ton working properly

 helm ls                          
Error: forwarding ports: error upgrading connection: error dialing backend: dial tcp 10.240.0.5:10250: getsockopt: connection timed out

but tiller seems to be deployed and running

I think there is same issue with dashboard

Proxy running on http://127.0.0.1:8001/
Press CTRL+C to close the tunnel...
error: error upgrading connection: error dialing backend: dial tcp 10.240.0.5:10250: getsockopt: connection timed out

[Zimmergren]

Possibly related to #224.

In issue #232 there's also some comments about helm and AKS causing the timeout issue you describe.

[jalberto]

Using az aks browse I can access k8s dashboard, but using kubectl proxy I get this error:

Error: 'tls: oversized record received with length 20527'
Trying to reach: 'https://10.244.1.3:9090/'

[shahiddev]

Temporary workaround: in the url that is opened in the browser about 1/2 way across in the url it says https - if you change that to http it should work.

[jalberto]

Thanks @shahiddev, that workaround works.

Still a bug, as I expect kubcetl command works well with AKS

[r-moiseev]

Thanks but therr is also bug with helm

[mboersma]

@r-moiseev if helm is still misbehaving for you, could you send details with subscription ID, resource group name, cluster name, and Azure region to [email protected] so we can investigate? Thanks!

[lalo]

@r-moiseev and for anybody else hitting this issue: this seems to be a bug with helm and a way to get around it is to kill the tiller pod.

So its:

• kubectl get pods --all-namespaces
• identify tiller-deploy pod and copy the name
• kubectl delete pods tiller-deploy-name
• another tiller pod should spawn and it should work now

[MaurGi]

you can use:

az aks browse --resource-group $rg --name $name --listen-port 8001