Stop passing variables Helm the wrong way
<p>In modern software development, Continuous Integration and Continuous Deployment (CICD) pipelines are essential. They allow for the automatic and consistent deployment of applications. The helm-set plugin is a valuable tool in this context, allowing you to pass (dynamic/secret) environment variables directly to your Helm deployments within a CICD pipeline without a need for source code changes. This functionality is heavily inspired by Terraform’s envsubst feature.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/0*R0N70Gm06psFu6Iu" style="height:467px; width:700px" /></p>
<p>Photo by <a href="https://unsplash.com/@michael_marais?utm_source=medium&utm_medium=referral" rel="noopener ugc nofollow" target="_blank">Michael Marais</a> on <a href="https://unsplash.com/?utm_source=medium&utm_medium=referral" rel="noopener ugc nofollow" target="_blank">Unsplash</a></p>
<h1>The old way</h1>
<p>Let’s assume you have a Helm chart named <code>my-chart</code> and you want to set the variable <code>replicaCount</code> to <code>3</code> when deploying a release. You can do this using the following command:</p>
<p><a href="https://xbery.medium.com/stop-passing-variables-helm-the-wrong-way-bb66e8dab127"><strong>Read More</strong></a></p>