helm init error

528 views
Skip to first unread message

LEO

unread,
Apr 11, 2017, 10:24:07 PM4/11/17
to kubernetes-sig-apps
When helm init, tiller cannot start.
I can find the msg from minion using 'docker logs tiller-contain':
Cannot initialize Kubernetes connection: Get http://localhost:8080/api: dial tcp 127.0.0.1:8080: getsockopt: connection refused

sendma...@gmail.com

unread,
Apr 13, 2017, 4:45:24 PM4/13/17
to kubernetes-sig-apps
Have same issue

simon....@brightcomputing.com

unread,
Aug 3, 2017, 9:56:41 PM8/3/17
to kubernetes-sig-apps
This is an old thread, but I'm going to post a reply as it has taken me days to figure this out.
In most cases this is caused by incorrect Kubernetes configuration.

However, I have a work around. Whether this is the correct way, I'm not sure.
Dump the tiller config....

helm init --debug --dryrun > tiller.yml

Set the Kubernetes master environment variable to the Kubernetes API server. Example master:8080
 spec:
      containers:
      - env:
        - name: TILLER_NAMESPACE
          value: kube-system
        - name: KUBERNETES_MASTER
          value: 'hostname:port'

kubectl create -f tiller.yml
Reply all
Reply to author
Forward
0 new messages