<p>As a new starter in the world of DevOps, I've tried to find a one-pager that explains side by side what each of the following technologies do best and how they are orchestrated together in typical deployment scenario. </p>

<p>Its all a bit overwhelming coming in cold.</p>

<p>Seems like there's a technology for every single step of the deployment. Have some been superseded by others? Are the differentiated in the granularity of the artifact?</p>

<p>No opinions please of which is better, just resources of hey they are used together.</p>

<ul>
<li>Docker</li>
<li>Kubernetes</li>
<li>Helm</li>
<li>Terraform</li>
<li>Rancher</li>
</ul>

RogerW
<p><strong>Docker</strong> is the de facto standard for building containers and running them in various environments.</p>
<p><strong>Kubernetes</strong> is a complex framework for orchestrating containers.</p>
<p><strong>Helm</strong> is a component of Kubernetes, a package manager for running apps on Kubernetes.</p>
<p>(<strong>Rancher</strong> is a framework for managing and orchestrating containers. It could also manage Kubernetes clusters)</p>
<p> </p>
<p>A typical scenario 'devops' scenario would involve builiding <strong>Docker</strong> images from source, and running them in A <strong>kubernetes</strong> cluster in production, as described in a <strong>Helm</strong> chart. The underlying infrastructure for Kubernetes could be deployed with <strong>Terraform</strong>.</p>
