Helm’s — atomic Option for Rollback Leaves You in the Dark
<p>The world of DevOps is an exciting journey full of exploration and problem-solving. As a DevOps enthusiast, I recently embarked on a new adventure into the realms of Kubernetes deployments. My trusty companion for this journey was Helm, the Kubernetes package manager. It promised seamless application deployments, and my initial experience was smooth sailing.</p>
<p>I harnessed the power of Helm charts to deploy my applications in a Kubernetes cluster, and I had a nifty command at my disposal:</p>
<pre>
helm upgrade - install -f values.yaml <release-name> . - atomic - timeout <timeout-sec></pre>
<p>This command made my deployments effortless and reliable.</p>
<p>The `<strong> — atomic</strong>` option acted like a safety net, ensuring that if anything went wrong during deployment, Helm would gracefully roll back to the previous version. It was a reassuring feature, much like a safety rope while climbing a steep mountain.</p>
<p><a href="https://medium.com/@akashjoffical08/helms-atomic-option-for-rollback-leaves-you-in-the-dark-73841d8a5842"><strong>Learn More</strong></a></p>