Kubernetes vagrant - unable to connect to api server

August 17, 2015

When running Kubernetes(K8s) vagrant(sometimes standalone installations), the vagrant up fails with the following error

Validating master
Validating minion-1
Waiting for each minion to be registered with cloud provider
error: couldn't read version from server: Get dial tcp connection refused

This implies the kubectl client is unable to connect to the kube-api server. This can happen due to a couple of reasons -

  • Prior K8s installation have left config trace in home directory. Delete the contents of ~/.kube directory, and re provision your vagrants.

  • The route for the kube-api server could be missing. Add the route

    #sudo route -nv add -net 10.245.1 -interface vboxnet0
    [Note: you should replace it with the subnet vagrant has created for you]

comments powered by Disqus