<p>Secondly ,  For deploying container images to kubernetes , we generally made deployment config(yaml files) .. </p>

<p>Now, these may different for staging and development environments . and with some new feature there may come some system environment variable , which needs to be present in yaml . </p>

<p>My question here is  . </p>

<pre><code>1. How yaml are managed , for example , manual efforts required if these is some change in yaml .
2. How it can be made automated . 
</code></pre>

Sahil Aggarwal
<p>use <a href="https://helm.sh/" rel="nofollow noreferrer">helm</a>, k8s package manager. helm will let you define a separated set of values for your environments (thanks  @xun for pointing that out)- development, canary, production etc,  and use them in a single yml <a href="https://helm.sh/docs/developing_charts/#charts" rel="nofollow noreferrer">chart</a>, which will be generated into a kubernetes regular <code>.yml</code> file.</p>

<p>helm will also let you share and use deployment-ready charts from the <a href="https://hub.helm.sh/" rel="nofollow noreferrer">helm hub</a> and the <a href="https://chartmuseum.com/" rel="nofollow noreferrer">chart museums</a>. </p>
