{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/helm/issues/1797","repository_url":"https://api.github.com/repos/kubernetes/helm","labels_url":"https://api.github.com/repos/kubernetes/helm/issues/1797/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/helm/issues/1797/comments","events_url":"https://api.github.com/repos/kubernetes/helm/issues/1797/events","html_url":"https://github.com/kubernetes/helm/issues/1797","id":199332315,"number":1797,"title":"Cannot connect to tiller from within pod","user":{"login":"bacongobbler","id":1360539,"avatar_url":"https://avatars.githubusercontent.com/u/1360539?v=3","gravatar_id":"","url":"https://api.github.com/users/bacongobbler","html_url":"https://github.com/bacongobbler","followers_url":"https://api.github.com/users/bacongobbler/followers","following_url":"https://api.github.com/users/bacongobbler/following{/other_user}","gists_url":"https://api.github.com/users/bacongobbler/gists{/gist_id}","starred_url":"https://api.github.com/users/bacongobbler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bacongobbler/subscriptions","organizations_url":"https://api.github.com/users/bacongobbler/orgs","repos_url":"https://api.github.com/users/bacongobbler/repos","events_url":"https://api.github.com/users/bacongobbler/events{/privacy}","received_events_url":"https://api.github.com/users/bacongobbler/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-01-07T01:55:02Z","updated_at":"2017-01-07T04:25:09Z","closed_at":"2017-01-07T04:25:09Z","body":"semi-related to #1723 I guess\r\n\r\nI found something quite curious while playing around with helm inside a pod. If no TTY is present when running `helm install` (such as with a `git push` inside the container), this is the output of `helm --debug install some-chart`:\r\n\r\n```\r\nError: Get http://localhost:8080/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp [::1]:8080: getsockopt: connection refused\r\n```\r\n\r\nNotice there was no debug information about a tunnel being created. However, If I `exec` into the container and run the same command:\r\n\r\n```\r\nk exec -it my-pod -- helm install /usr/local/share/chart.shim --debug\r\nCreated tunnel using local port: '36717'\r\nSERVER: \"localhost:36717\"\r\nCHART PATH: /usr/local/share/chart.shim\r\nNAME:   invited-dachshund\r\nREVISION: 1\r\nRELEASED: Sat Jan  7 01:43:17 2017\r\nCHART: appname-v0.1.0\r\nUSER-SUPPLIED VALUES:\r\n...\r\n```\r\n\r\nSo there seems to be a condition which causes helm to not create a tunnel to tiller running over in the kube-system namespace.\r\n\r\nOn a related note, is there a reliable way to set $HELM_HOST inside a pod so helm doesn't need to spawn a tunnel to tiller? Or should I just spawn a tiller instance inside the pod as well? Mostly concerned about data persistence between pod restarts, but if tiller's state is all stored in configmaps then that'd be a happy medium."},"comment":{"url":"https://api.github.com/repos/kubernetes/helm/issues/comments/271061895","html_url":"https://github.com/kubernetes/helm/issues/1797#issuecomment-271061895","issue_url":"https://api.github.com/repos/kubernetes/helm/issues/1797","id":271061895,"user":{"login":"bacongobbler","id":1360539,"avatar_url":"https://avatars.githubusercontent.com/u/1360539?v=3","gravatar_id":"","url":"https://api.github.com/users/bacongobbler","html_url":"https://github.com/bacongobbler","followers_url":"https://api.github.com/users/bacongobbler/followers","following_url":"https://api.github.com/users/bacongobbler/following{/other_user}","gists_url":"https://api.github.com/users/bacongobbler/gists{/gist_id}","starred_url":"https://api.github.com/users/bacongobbler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bacongobbler/subscriptions","organizations_url":"https://api.github.com/users/bacongobbler/orgs","repos_url":"https://api.github.com/users/bacongobbler/repos","events_url":"https://api.github.com/users/bacongobbler/events{/privacy}","received_events_url":"https://api.github.com/users/bacongobbler/received_events","type":"User","site_admin":false},"created_at":"2017-01-07T04:25:09Z","updated_at":"2017-01-07T04:25:09Z","body":"nope, this is due to user error. container is running as a different user so helm can't reach kubernetes because the proper envvars aren't present in the environment."}}
{"actor":{"display_login":"bacongobbler"}}