<p>This may sound like a n00b question, and maybe it is, but some things with the Azure Container Services puzzle me a little. I have managed to get a Kubernetes Cluster up and running on Azure inside a Resource Group, so for starters I am set and done.</p>

<p>Now my questions are the following:</p>

<ul>
<li>Who will take care of patching and upgrading the Master and Agent VMs?</li>
<li>Who will take care of patching and updating the Kubernetes Components?</li>
<li>Will I need to take care of backing up the <code>etcd</code> database myself?</li>
<li>Do I get an SLA with the Kubernetes Cluster, or is everything on top of the VM SLAs all up to me (i.e. making sure Kubernetes behaves)?</li>
</ul>

<p>I have the feeling the answers to these questions are "me", "me", "yes" and "no", which would make me ask myself whether the ACS is just a set of Resource Manager Templates, or where's the added value? Am I right on my assumptions, or where am I wrong?</p>

<p>I'm on the Azure Container Service team, and your statement:</p>

<p>"ACS is just a set of Resource Manager Templates"</p>

<p>Is more or less correct at this moment in time (Jan. 2017)</p>

<p>Over the course of the next few months, we will be improving support for all of the scenarios you mentioned:
  * Backup
  * Upgrade
  * Health maintainence and repair</p>

<p>And this applies not just to Kubernetes but also to DC/OS and Docker Swarm which are also supported in ACS.</p>

<p>Please let me know if I can help with more information.</p>
