<p>What is the correct way to install <a href="https://github.com/kubernetes/kubernetes/tree/release-1.1/cluster/addons" rel="noreferrer">addons</a> with Kubernetes 1.1? The <a href="https://github.com/kubernetes/kubernetes/tree/release-1.1/cluster/addons" rel="noreferrer">docs</a> aren't as clear as I'd like on this subject; they seem to imply that one should copy addons' yaml files to /etc/kubernetes/addons on master nodes, but I have tried this and nothing happens.</p>

<p>Additionally, for added confusion, the docs imply that addons are bundled with Kubernetes:</p>

<blockquote>
  <p>So the only persistent way to make changes in add-ons is to update the manifests on the master server. But still, users are discouraged to do it on their own - they should rather wait for a new release of Kubernetes that will also contain new versions of add-ons.</p>
</blockquote>

<p>So, how should I really install addons, f.ex. <a href="https://github.com/kubernetes/kubernetes/tree/release-1.1/cluster/addons/cluster-loadbalancing" rel="noreferrer">cluster-loadbalancing</a>, with Kubernetes 1.1?</p>

<blockquote>
  <p>... they seem to imply that one should copy addons' yaml files to /etc/kubernetes/addons on master nodes, but I have tried this and nothing happens.</p>
</blockquote>

<p>This is only true if you are using one of the salt-based installation mechanisms. </p>

<blockquote>
  <p>So, how should I really install addons, f.ex. cluster-loadbalancing, with Kubernetes 1.1?</p>
</blockquote>

<p>Most of the add-ons can be installed by just running <code>kubectl create -f</code> against the replication controller and service files for the add-on. You need to create the <code>kube-system</code> namespace first if you haven't already, and some of the add-ons (like <a href="https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/skydns-rc.yaml.in" rel="nofollow">dns</a>) require you to fill in a few values in a jinja template that would otherwise be handled by salt. </p>
