<p>I am learning kubernetes. 
I have a few simple containers with secrets. Lets say I have two services , I can put them in a deployment, add an ingress and put all of those in a bash script and run</p>

<pre><code>kubectl apply -f deployment1
kubectl apply -f deployment2
kubectl apply -f ingress
</code></pre>

<p>Now let's say I put this in helm. What do I gain here by putting this in a <code>helm</code> chart ? </p>

<p>In comparison to bash / shell based kubectl apply -f for a list of manifests, helm offers:</p>

<ul>
<li>atomic role out</li>
<li>templating (conf injection)</li>
<li>upgrade and atomic role back</li>
<li>atomic deletion of all associated ressources</li>
</ul>

<p>Basically helm offers the ability to create deployment artifacts which are parametrized and full lifecycle management. </p>
