-
Notifications
You must be signed in to change notification settings - Fork 307
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
Comments
I should mention, when I try helm upgrade on a chart I get:
|
From kubernetes/helm: It seems helm does a port forward with tiller for communication:
This throws the same error:
Is it a firewall issue with the pod network? |
Probably a duplicate of #434 |
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. |
Yes it works now. Thanks! |
facing issue while connecting the tiller in EKS ... |
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 resultsOn 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):Output of
kubectl version
:Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AKS v1.9.6
The text was updated successfully, but these errors were encountered: