Skip to content

Instantly share code, notes, and snippets.

@isweluiz

isweluiz/helm-introduction.md

Created July 31, 2023 09:04
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save isweluiz/a4da8d6bdcbe05e5fa5f0621c8cc2161 to your computer and use it in GitHub Desktop.
Save isweluiz/a4da8d6bdcbe05e5fa5f0621c8cc2161 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
helm-introduction.md

The video titled Introduction to Helm | Kubernetes Tutorial | Beginners Guide provides a comprehensive introduction to Helm, a package manager for Kubernetes. Below a summary of the key points:

  1. What is Helm?: Helm is a package manager for Kubernetes. It allows you to bring all of your YAML files together in what's called a chart. A chart can have a name, a description, and a version. A chart groups all these YAML files together in a templates folder.

  2. Why use Helm?: Helm is used to manage Kubernetes YAML files, which describe everything in Kubernetes, such as deployments, pods, services, config maps, secrets, and more. Helm makes these YAML files reusable, allowing you to inject parameters into them and reuse them among many applications and microservices.

  3. Creating a Helm Chart: A Helm chart is a unit of deployment made up of a set of YAML files. It can be for a microservice or any software like Redis, MySQL, Prometheus, etc. You can create a Helm chart by moving your existing applications or microservices into the templates directory of the chart.

  4. Using Helm Chart: Once you've created a Helm chart, you can install it by using the command helm install and passing in the name of your chart and the folder where the chart is located. Helm will then install everything that's part of that chart into your Kubernetes cluster.

  5. Templating in Helm: Helm uses a templating engine that allows you to replace hard-coded values in your chart with variables. This makes your chart more generic and reusable. You can also use if-else statements within your Helm chart for more complex template generation.

  6. Helm's Powerful Template Generation Capability: Helm's template generation capability allows you to forcefully roll out new pods when a config map changes. This is useful because by default in Kubernetes, when a config map changes, pods are not automatically restarted.

  7. Control Flow in Helm: Helm allows you to do control flow, such as if and else statements, to generate more complex YAML based on the values you pass in. It also allows you to set defaults.

  8. Making Helm Chart More Generic: You can make your Helm chart more generic by allowing the user to override values at the time of deployment. This can be useful if you want to deploy more complex software like Redis or RabbitMQ clusters, or if you want to create a chart to allow your teams to deploy their microservices and share the same chart among many services.

  9. Helm Upgrade: The helm upgrade command allows you to roll out changes to your application. When you run this command, Helm will roll out a new deployment, and the old pods will start terminating while new pods start up.

  10. Alternatives to Helm: If you're looking for an alternative to Helm that's maybe a little bit less complex, you can check out Kustomize, which allows you to do very similar things.

Please note that the video is divided into two parts, and this summary is based on the key highlights extracted from the video. For more detailed information, it would be best to watch the video or request a summary of a specific part of the video.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment