Hi, Let us understand about
Helm, the package manager for kubernetes, whenever an application needs to be deployed within kubernetes cluster
It involves n number of components and organising those components in the right order for the right dependencies
and deploying the right version into the cluster
After testing, it's going to be a challenging task depending on the size of the application.
And here's where the helm will facilitate to deploy the entire package into the kubernetes cluster.
And it's going to visualize the application as a package where all the dependencies will be packed
together and the entire package can be shared as well as deployed into the kubernetes cluster.
Also, it facilitates to upgrade and roll back the changes by maintaining the versions.
We can visualize helm like APT or yum package managers available within the Linux world, and it
automates the version handling as well as automate the deployment
upgrade and roll back of various versions
And the entire package can be packaged as a file and it can be shared with the team members or with other teams.
The main concept of helm is about templatisiinig the deployment descriptor so that the values that
are going to get changed for different environments can be fed as an input value or as a separate value files.
So the templates can be stored within the repositories and only the
Values that are going to get changed depending on the environment, can be maintained in different files
and the required files can be provided as a input.
So basically, helm can handle the entire lifecycle of the application.
Right, from creating, installing, upgrading, rollback
delete, status maintenance as well as version handling of the applications.
So overall, helm going to provide the following benefits, that is repeatability, reliability, and
it can manage multiple environments with the same templates
And it's going to facilitate easy collaboration as everything will be defined within the files and
no configurations will go out of the file.
So the entire file can be versioned and it can be integrated easily with the CICD environment and it can
handle any complex environment
within the production world. As a part of this particular course, we will be seeing all the features that
are listed over here.
That is automation of upgrade, roll back, templatizing for different environments as well as involving
helm in different stages, creating our own custom repositories and lot more.
So don't worry about the terminologies that I have used over here.
We are going to have detailed discussion on each and every topic by using a production grade, kubernetes
cluster, and we will be seeing the simple scenario to complex scenario of helm.