<p>I've successfully deployed a Kubernetes 1.3.5 cluster on 1 master + 6 nodes (all running CentOS) including the DNS and Kubernetes Dashboard addons. Everything seemed to be working OK at first. However, when I tried to run</p>

<pre><code>kubectl proxy --address=&lt;master-external-ip&gt; --port=9090 --disable-filter
</code></pre>

<p>and access <code>http://&lt;master-external-ip&gt;:9090/ui</code> I got the following output</p>

<pre><code>Error: 'dial tcp 172.16.38.2:9090: i/o timeout'
Trying to reach: 'http://172.16.38.2:9090/'
</code></pre>

<p>However, if I start <code>flanneld</code> on the master everything works and I can actually reach the Dashboard. Now, I've used <code>kube-up.sh</code> to install the cluster and it didn't install any configs or <code>systemd</code> service for Flannel, which leaves me confused—should Flannel also run on the master?</p>

<p>Yes, it should, otherwise packets going through the API server proxy can not be routed to their final destination: the dashboard pod running on some other machine.</p>
