Helm (an incubated CNCF project) is the kubernetes package manager which allows you to parametrize, version and publish your kubernetes applications. However, Helm is NOT the kubernetes CI/CD tool. And that’s why we created Helmsman.
We use Helmsman to automate the lifecycle management of Helm releases in k8s clusters using a declarative desired state. The desired state describes how we would like to setup the cluster and deploy the applications. By version controlling our desired states and using a CI tool we can achieve GitOps ( in plain English: trigger changes from git commits).
In this talk, I will explain why we need Helmsman, how it works and how it can be used together with CI tools to achieve GitOps. I will run a demo using Google Kubernetes Engine (GKE) and CircleCI (though any k8s provider and CI tool will work the same).
17:30 - 17:45 Meet & Greet
17:45 - 18:00 Brief introduction to Helm
18:00 - 18:15 Why GitOps?
18:15 - 18:30 GitOps with Helm? What’s missing?
18:30 - 18:50 Break
18:50 - ~19:30 Introducing Helmsman and demo
Sami is a DevOps consultant at Praqma where he supports clients with tasks like: automation, infrastructure as code, secrets management, kubernetes and Helm. He holds a PhD in Computing Science from Newcastle University, UK and has previous experience in teaching, research and software development.