HELM Introduction, Package manager need and purpose
-
Helm is a tool that streamlines installing and managing Kubernetes applications. Think of it like Apt/Yum/Homebrew for K8S.
-
Helm uses a packaging format called charts. A chart is a collection of files that describe a related set of Kubernetes resources. A single chart might be used to deploy something simple, like a memcached pod, or something complex, like a full web app stack with HTTP servers, databases, caches, and so on.
-
automated version handling during upgrade/rollback of a application
-
store, search and reuse the templates
Benefits
- Repeatability
- Reliability
- manage multiple environment deployment by just changing values.yaml
- manage any complex environments
Package manager need and purpose
-
Assume like you are deploying application which has lot of components like secrets, config maps, pv, pvc and many more in that case all the files should be deployed in organized manner, helm make these kind of deployment very easy.
-
Assume the application should be deployed across multiple environments, in that case values like port, targetport, metadata, replica count, many other thigs might vary. in this case if you dont use helm then you need to have 2 versions of yaml files for different environments. if you use helm, there is no need of changing actual manifest file, its just we need to change the values.yaml for different environments.
below are sample pictures which gives better idea
if you use kubernetes
if you use helm charts
