<p>I have been going through this to get started with Kubernetes, running on Mac OS v 10.9.5, Vagrant v 1.7.4, VirtualBox v 4.3.28, and Kubernetes v 1.0.3.:
<a href="https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/vagrant.md">https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/vagrant.md</a></p>

<p>Full install log can be found here:
<a href="http://mcdonaldland.info/files/kubernetes/install-log.txt">http://mcdonaldland.info/files/kubernetes/install-log.txt</a></p>

<p>I've tried both the download and sh install versions of this.</p>

<p>I've run this multiple times and every time it gets to the "waiting for each minion to be registered with cloud provider" step and loops forever. Eventually, I "CTRL+C" and exit the script. In looking at the source it obviously has something to do with the nodes not being found, but I can't figure out why it cannot find them.</p>

<p>After killing the script, running 'kubectl get nodes' returns nothing. The same happens if I used the SH script. </p>

<p>If I am in the ~/kubernetes/cluster director and run 'vagrant ssh master' or 'vagrant ssh minion-1' I can connect to them. If I run some scripts to add pods I can get them to register. Same with Replication Controllers. </p>

<p>When I check status the pods will never start. When I dig into the logs it appears that the nodes cannot be connected to (aka found) and the minions are erroring on startup.</p>

<p>I have been struggling for 5 days now to figure out why my nodes are not showing up / registering properly. I figure I'm missing something simple but am at a loss now. </p>

<p>Any help is appreciated. Thanks in advance.</p>

<p>The reason is a bug in kubernetes. It <a href="https://github.com/kubernetes/kubernetes/issues/12854" rel="noreferrer">seems to be a TLS error</a>.</p>

<p>If you manually download <a href="https://github.com/kubernetes/kubernetes/releases/tag/v1.0.1" rel="noreferrer">kubernetes 1.0.1</a> you will get closer. However, there's been a bugfix that you'll need to patch into 1.0.1 to make it work properly with vagrant. Otherwise, network provisioning will not work and you'll run into <a href="https://github.com/kubernetes/kubernetes/issues/12285#issuecomment-128613056" rel="noreferrer">this issue</a>. </p>

<p>So, as suggested there, apply <a href="https://github.com/kubernetes/kubernetes/pull/12237/files" rel="noreferrer">these changes</a> to the provision scripts of v1.0.1 and you'll be good to go. Simple, right?</p>
