<p>I have read some introduction of these projects, but still cannot get a clear idea of the difference between Kubernetes and Flynn/Deis. Can anyone help?</p>

<p>Kubernetes is really three things:</p>

<ul>
<li>A way to dynamically schedule containers (actually, sets of containers called pods) to a cluster of machines.</li>
<li>Manage and horizontally scale a lot of those pods using labels and helpers (ReplicationController)</li>
<li>Communicate between sets of pods via services, expose a set of pods externally on a public IP and easily consume external services.  This is necessary to deal with the horizontal scaling and the dynamic nature of how pods get placed/scheduled.</li>
</ul>

<p>This is all very much a tool set for managing compute across a set of machines.  It <em>isn't</em> a full application PaaS.  Kubernetes doesn't have any idea what an "application" is.  Generally PaaS systems provide an easy way to take code and get it deployed and managed as an application.  In fact, I expect to see specialized PaaS systems built on top of Kubernetes -- that is what RedHat OpenShift is doing.</p>

<p>One way to think about Kubernetes is as a system for "logical" infrastructure (vs. traditional VM cloud systems which are  </p>
