<p>I am trying to setup a small Kubernetes cluster using a VM (master) and 3 bare metal servers (all running Ubuntu 14.04). I am following the Kubernetes <a href="https://github.com/kubernetes/kubernetes/blob/release-1.0/docs/getting-started-guides/ubuntu.md" rel="nofollow">install tutorial for Ubuntu</a>. Everything works fine if I use the 4 nodes (VM + servers) as minions. But when I try to use the VM as just a master, it cannot access the Flannel network. I can create pods, services, etc, but if I try to access a service from the master node (VM), it cannot find the Flannel's IP.</p>

<p>Can I include a master only node to the Kubernetes' internal network (Flannel's net in this case)? If not, any advice in how to access the Kubernetes UI and other services from the master node?   </p>

<p>To have the master node access the cluster network, you can run <code>flanneld</code> and <code>kube-proxy</code> on the master node. This should give you the access you need.</p>

<p>However, adding these components in the context of using the <code>kube-up.sh</code> method may be a little involved. Seems like you may have a few options while remaining mostly within the framework of that tutorial:</p>

<ul>
<li>You could walk through the <code>kube-up.sh</code> scripts and alter it so that it installs and configures <code>kube-proxy</code> and <code>flanneld</code> on the master node, but not the <code>kubelet</code>. That may be hard to maintain over time.</li>
<li>You could bring up the cluster as you already have with all 4 nodes running as 'nodes' (the new name for workers that used to be called 'minions'). Then mark the master node as unschedulable (<code>kubectl patch nodes $NODENAME -p '{"spec": {"unschedulable": true}}'</code>) as outlined <a href="https://github.com/kubernetes/kubernetes/blob/5c903dbcacb423158e3f363bcbb27eef58f95218/docs/admin/node.md#manual-node-administration" rel="nofollow">here</a>. The master will still show up in node listings and such, but it should not get any pods scheduled to it and should have full network access to the cluster.</li>
<li>You could also bring the cluster up as you already have with 4 nodes and then just log in and remove the <code>kubelet</code> on the master. This is effectively like the above, except the master won't show up in node listings (although you may have to remove it (<code>kubectl delete node $NODENAME</code>) when you remove the kubelet.</li>
</ul>

<p>There are probably other options (there always are!), but hopefully these can get you started.</p>
