- Introduction
- Helm Charts and Releases
- Helm Templates and Values
- Helm Chart Dependencies and External Charts
- How to use Helm Hooks for Fun and Profit
- Top-3 Helm Plugins: Helm Secrets, Helm Diff and Helm Git
In this course, you will learn the basic concepts of Helm, what is it used for and, most importantly, why you might need.
This course assumes you already know what Kubernetes is, as well some of it’s primary resource types, like Pods, Deployments, Services, ConfigMaps and Secrets. If you’ve never used Kubernetes before, you will hardly benefit from this lightning course.
Helm is a package manager for Kubernetes. This description, taken from the Helm website, doesn’t really say much. Let’s look at this from the different angle.
When you deploy an application to Kubernetes, you end up with lots of YAML files - you need a YAML file for the Deployment, for the Service, for some ConfigMaps and so on, for every object that your application needs. Of. course, you could also have all of those in a single big YAML file, but that’s not the point here.
Many of those objects depend on each other in some way or another - Service finds Pods by labels, and those labels should be the same ones configured in your Deployment’s pod template. Deployment also needs to mount correct ConfigMap, and same goes for PersistentVolumes.
Quite naturally, you want to configure many, if not all, of those objects depending on the environment - staging Deployment might have different number of replicas, and production Secret for sure will have a different database password.
In addition, you also need a simple way to rollback to a previous version, and maybe execute some hooks before and after different stages of the rollout - for example, you might need to run database migrations before deploying the new release.
Helm is the tool that solves those and few other problems. It allows you to properly template your object definitions, it gives you a set of commands to manage the releases of your application and it provides some extra advanced utilities, like aforementioned hooks.
While definitely not the only tool that solves all or some of those problems, Helm became more or less a standard for packaging Kubernetes object definitions. As a result, almost every software you want to install has an existing Helm package - called chart - that simplifies both installation and updates of this software.
This is why Helm is the package manager for Kubernetes - not only due to its features, but also because of how widespread it is. In this course, we will learn how to use it.
Build your English communication skills for professional success
Learn the Secrets that will Transform your Photos & Make Your Images Pop using Photoshop & Lightroom
ChatGPT Prompt Engineering from Basic to advance and make customize ChatBot with OpenAI ,ChatGPT and Google Colab(free)
Quick refresher on basics of HTML, CSS, JavaScript
mkdev is a Public Cloud (AWS & GCP) and Cloud Native consulting, based in Munich. We are here to boost your productivity, reduce cloud costs and complexity, and enhance your standing as a true tech leader. We do it with Cloud Native technologies*, deep Automation and the DevOps spirit. Let's have a call.
We do not pursue a status of a partner with the Big Tech, or any technology provider. We don't get paid for recommending you anything, neither we get a fee from increasing your monthly cloud spend. Our only partners are our clients. This is how we partner:
1. Time-tested solutions
We never play around at your expense. We bring time-tested, verified by us and the industry technologies and solutions, the ones that make sense for you, not the ones that are trending at this second. The systems and setups we design and build are meant to get the job done, not to impress — but it doesn't meant we won't impress you.
2. Tailored to your business
The knowledge and experience that we share is not only battle-tested, but also relevant in the context of your objectives and your team. We always thoroughly analyze your capabilities, goals and business environment before offering and implementing any solutions.
3. We leave you prepared
Every project comes to an end. Projects with us end with a detailed hand-over and world-class documentation. We always make sure, that your team is ready to act on their own, long after we are gone.
We believe in making knowledge as accessible as possible, thus we produce and share our content and courses for free.
* AWS, GCP, OpenShift/Kubernetes, GitOps, Containers, CI/CD, Serverless, Microservices, you know the drill.