/k8s_basics/helm/index.html Intro Helm describes itself as “The package manager for Kubernetes”. An excerpt taken from the official Helm website describing what that means: Helm helps you manage Kubernetes applications — Helm Charts help you define, install, and upgrade even the most complex Kubernetes application. Charts are easy to create, version, share, and publish — so start using Helm and stop the copy-and-paste. Helm is a graduated project in the CNCF and is maintained by the Helm community. Hugo en-US /k8s_basics/helm/charts/index.html Mon, 01 Jan 0001 00:00:00 +0000 /k8s_basics/helm/charts/index.html In the previous chapters when dealing with Kubernetes, we learned how to create and manage a bunch of different Kubernetes components and applications by using yaml files. As you can imagine handling multiple yaml files for every single application can get quite cumbersome once you have more than just two or three deployments in parallel. It’s a lot of steps you have to take to get everything up and running, and handling versioning between the different moving parts can be difficult at times. /k8s_basics/helm/templating/index.html Mon, 01 Jan 0001 00:00:00 +0000 /k8s_basics/helm/templating/index.html In the last chapter we successfully deployed multiple Kubernetes components with a single Helm chart. In this chapter we will be discussing how we can create our own configuration files called values.yaml and how we can use a custom values file to override those of public helm charts. Exercise - Basic templating values.yaml is a plain yaml file that contains default configuration values for the helm templates. These values will later be referenced in the templates and can be overridden with the helm install command. /k8s_basics/helm/dependencies/index.html Mon, 01 Jan 0001 00:00:00 +0000 /k8s_basics/helm/dependencies/index.html In this chapter we’ll look at bundling charts together with subcharts and dependencies. This allows us to create a single release bundling all applications (frontend, backend and the database). Exercise - Deploying the application in separate releases In the last section we looked at how we can create a Helm chart from scratch to deploy our database. Now we are going to deploy the remaining components todobackend and todoui as well. Fortunately there are already helm charts prepared so we don’t have to create those now. When you look at those charts with