<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.):<br>
NA</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.):</p>
<h2 dir="auto">NA</h2>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):<br>
Feature Request</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):<br>
1.3.x 1.4.x master</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: vSphere</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): Linux</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): NA</li>
<li><strong>Install tools</strong>: kube-up.sh</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
Currently the networking setup when deploying using kube-up is manual and not fleshed out. The routes get setup manually for the CIDR on each node. This has prone to be buggy based on past experience.</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
Use and configure a networking plugin such as flannel or weaveworx</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):<br>
use kube-up.sh to deploy on vSphere.</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:</p>
<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.): No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.): daemonset, kubectl</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one): Bug report<br>
<strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;4&quot;, GitVersion:&quot;v1.4.2&quot;, GitCommit:&quot;c072cc2ee4dfc21b60196e5994c56c40e1c29b93&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-10-15T00:13:29Z&quot;, GoVersion:&quot;go1.6.3&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;4&quot;, GitVersion:&quot;v1.4.0&quot;, GitCommit:&quot;a16c0a7f71a6f93c7e0f222d961f4675cd97a46b&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-09-26T18:10:32Z&quot;, GoVersion:&quot;go1.6.3&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}"><pre class="notranslate"><code class="notranslate">Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.2", GitCommit:"c072cc2ee4dfc21b60196e5994c56c40e1c29b93", GitTreeState:"clean", BuildDate:"2016-10-15T00:13:29Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:10:32Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
</code></pre></div>
<p dir="auto">Also tested with:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;4&quot;, GitVersion:&quot;v1.4.1&quot;, GitCommit:&quot;33cf7b9acbb2cb7c9c72a10d6636321fb180b159&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-10-10T18:19:49Z&quot;, GoVersion:&quot;go1.6.3&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}
Server Version: version.Info{Major:&quot;1&quot;, Minor:&quot;4&quot;, GitVersion:&quot;v1.4.0&quot;, GitCommit:&quot;a16c0a7f71a6f93c7e0f222d961f4675cd97a46b&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2016-09-26T18:10:32Z&quot;, GoVersion:&quot;go1.6.3&quot;, Compiler:&quot;gc&quot;, Platform:&quot;linux/amd64&quot;}"><pre class="notranslate"><code class="notranslate">Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.1", GitCommit:"33cf7b9acbb2cb7c9c72a10d6636321fb180b159", GitTreeState:"clean", BuildDate:"2016-10-10T18:19:49Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:10:32Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}
</code></pre></div>
<p dir="auto"><strong>Environment (server)</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: AWS</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): Debian Jessie</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): Linux ip-10-64-61-28 4.4.23-k8s <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="35192559" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/1" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/1/hovercard" href="https://github.com/kubernetes/kubernetes/issues/1">#1</a> SMP Fri Sep 30 13:51:02 UTC 2016 x86_64 GNU/Linux</li>
<li><strong>Install tools</strong>: kops with <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="181864954" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kops/issues/621" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes/kops/pull/621/hovercard" href="https://github.com/kubernetes/kops/pull/621">kubernetes/kops#621</a> applied</li>
</ul>
<p dir="auto"><strong>Environment (client)</strong>:</p>
<ul dir="auto">
<li><strong>OS</strong> (e.g. from /etc/os-release): Arch Linux</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): Linux ****** 4.7.0-1-ARCH <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="35192559" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/1" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/1/hovercard" href="https://github.com/kubernetes/kubernetes/issues/1">#1</a> SMP PREEMPT Mon Aug 8 22:05:58 CEST 2016 x86_64 GNU/Linux</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
When applying Calico's deployment YAML file, the daemonset isn't sent to the server</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ kubectl apply -f  https://raw.githubusercontent.com/projectcalico/calico/master/master/getting-started/kubernetes/installation/hosted/calico.yaml
configmap &quot;calico-config&quot; configured
secret &quot;calico-etcd-secrets&quot; configured
replicaset &quot;calico-policy-controller&quot; configured"><pre class="notranslate"><code class="notranslate">$ kubectl apply -f  https://raw.githubusercontent.com/projectcalico/calico/master/master/getting-started/kubernetes/installation/hosted/calico.yaml
configmap "calico-config" configured
secret "calico-etcd-secrets" configured
replicaset "calico-policy-controller" configured
</code></pre></div>
<p dir="auto">However, when extracting the daemonset config to separate file, apply works properly:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ cat daemonset.yaml
# This manifest installs the calico/node container, as well
# as the Calico CNI plugins and network config on
# each master and worker node in a Kubernetes cluster.
kind: DaemonSet
apiVersion: extensions/v1beta1
metadata:
 name: calico-node
...
$ kubectl apply -f daemonset.yaml
daemonset &quot;calico-node&quot; configured"><pre class="notranslate"><code class="notranslate">$ cat daemonset.yaml
# This manifest installs the calico/node container, as well
# as the Calico CNI plugins and network config on
# each master and worker node in a Kubernetes cluster.
kind: DaemonSet
apiVersion: extensions/v1beta1
metadata:
 name: calico-node
...
$ kubectl apply -f daemonset.yaml
daemonset "calico-node" configured
</code></pre></div>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
All 4 documents in the YAML file should be applied</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):<br>
Unfortunately I haven't managed to create smaller test case than the original calico.yaml.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/e49b8fd9d349b0465a261633f5f4788618d36301/master/getting-started/kubernetes/installation/hosted/calico.yaml"><pre class="notranslate"><code class="notranslate">$ kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/e49b8fd9d349b0465a261633f5f4788618d36301/master/getting-started/kubernetes/installation/hosted/calico.yaml
</code></pre></div>