<p>I am new to Kubernetes and been looking at it as an option for a specific solution. </p>

<ul>
<li>We have a scenario where we have 100+ physical machines running RHEL distributed across different locations.</li>
<li>There is a plan to deploy and manage docker based containers on each of these machines. Let's group these containers as Pod A.</li>
<li>Now each of these machines require an instance of Pod A running on them and automatically synchronise if there are any changes.</li>
<li>Over time new machines maybe added and they will need to automatically get Pod A running on them as well.</li>
</ul>

<p>I understand the idea behind Kubernetes is to abstract the machine and OS layer but in this case we can't do that. So I guess I have a few questions around this: -</p>

<ul>
<li>Is Kubernetes the correct choice here? Are we breaking the fundamental concept behind it?</li>
<li>Is it possible to tag each machine as an identifiable node?</li>
<li>Target a specific Pod to a subset of nodes?</li>
</ul>

<p>Are there any similar examples available?</p>

<p>There is a resource named <a href="https://github.com/kubernetes/kubernetes/blob/master/docs/design/daemon.md" rel="nofollow">daemonset</a> that spawn at least a pod per node, on a new node added the pod will be spawn on it automatically. </p>

<p>About update, change the image in the resource daemonset and all pods will be updated. </p>
