Member-only story
CI/CD & Automation: Helm Charts in GitHub Actions with KinD and Self-Signed Certificates
Anyone who knows me knows how much I enjoy automation. Anything I can automate, I will. The CI/CD process is one of those places I rely heavily on as a result of this. Anything I can test in my pipelines, I will. Helm Charts are no exception to this rule. In today’s article, I will be showing how you can leverage KinD inside your GitHub Actions to automatically test your Helm Charts and ensure everything works as expected. Let’s peel this onion and get learning!
It is worth noting that I usually use GitLab over GitHub. As a result, you may see some differences in my style as I’m using a GitLab Runner style for my Actions. You are of course encouraged to use whatever style you prefer.
Why should you test your Helm Charts in CI/CD?
Something interesting I have seen is that many people are surprised at the idea of testing your charts in the CI/CD. This is a no-brainer for me. It’s no different than adding your unit testing to your CI/CD. Testing your charts is as simple as running them and verifying that everything starts as expected. You can even go so far as to leverage the helm built-in ‘test’ folder. By doing this simple execution, you can confirm that it works as intended before merging in, and even can go so far…
