1 00:00:00,000 --> 00:00:05,966 Hi 2 00:00:05,966 --> 00:00:11,599 Let's have a quick overview on various components of helm. When it comes to helm 3 00:00:11,600 --> 00:00:19,100 The main components with which we are going to interact is helm client and we can install helm client in any system 4 00:00:19,100 --> 00:00:24,766 And once the installation is done, that's going to facilitate the interaction between the user and the 5 00:00:24,766 --> 00:00:31,166 helm components, as well as it's going to facilitate the communication to the kubernetes cluster. 6 00:00:31,166 --> 00:00:37,699 And the next important component of helm is the charts that's going to be the building block of the entire 7 00:00:37,700 --> 00:00:43,933 helm where the entire application definition will be made within the charts and the charts provides various 8 00:00:43,933 --> 00:00:49,233 features, how the applications can be defined within the kubernetes environment. 9 00:00:49,233 --> 00:00:57,199 And it has collection of files, different structures to define values and how to build a sub chart 10 00:00:57,200 --> 00:01:01,700 and to represent any complex environment within the kubernetes cluster. 11 00:01:01,700 --> 00:01:07,600 It has the options and we will be having lots and lots of detailed discussion about each and every component 12 00:01:07,600 --> 00:01:09,466 available within the charts. 13 00:01:09,466 --> 00:01:15,132 So charts are nothing but how a kubernetes application should get deployed within the kubernetes cluster. 14 00:01:15,133 --> 00:01:17,199 That's going to be the definition file 15 00:01:17,200 --> 00:01:21,433 And once the file is created, we need to manage the files 16 00:01:21,433 --> 00:01:27,799 So that can be shared with other team members as well as the next version can be created. 17 00:01:27,800 --> 00:01:30,133 And that we call it as repositories. 18 00:01:30,133 --> 00:01:36,233 Repositories are nothing but a storage environment where various charts of various applications can be 19 00:01:36,233 --> 00:01:41,966 stored and can be shared with other members within the team or across the teams. 20 00:01:41,966 --> 00:01:48,399 And once the chart is released into the environment, that instance we call it as release and we 21 00:01:48,400 --> 00:01:55,300 can have multiple versions of release in multiple environment and all that will be managed by the helm client. 22 00:01:55,300 --> 00:02:02,166 What releases installed, in what environment, what values were used and any value that I wanted to 23 00:02:02,166 --> 00:02:06,966 change and make a next upgrade of the release or rollback of the release 24 00:02:06,966 --> 00:02:14,299 Everything will be handled and release is nothing but the instance of a chart that is deployed into the environment. 25 00:02:14,300 --> 00:02:21,433 So if I had to collaborate all these terminologies as a workflow, we can visualize it this way 26 00:02:21,433 --> 00:02:28,133 I can have n number of chart files and the chart files will be packaged together using the helm or basically 27 00:02:28,133 --> 00:02:32,166 the helm will facilitate us to create that as a package. 28 00:02:32,166 --> 00:02:37,666 Once the packages available, I can store within the repositories and the repositories will facilitate 29 00:02:37,666 --> 00:02:39,799 to store the charts 30 00:02:39,800 --> 00:02:44,833 Once the helm packages it, I can store it within the repository. 31 00:02:44,833 --> 00:02:50,566 Once the charts are available within the repositories, I can package them as a tar file where all the 32 00:02:50,566 --> 00:02:57,432 dependent files of the charts will be put within a single zipped file and it can be sent to the external 33 00:02:57,433 --> 00:03:00,799 world or store it in a different environment. 34 00:03:00,800 --> 00:03:07,400 And once if I have the charts within the repository, I can use them and create an application and deploy 35 00:03:07,400 --> 00:03:09,400 it into the cluster. Here 36 00:03:09,400 --> 00:03:13,300 The management of the entire lifecycle of the application will be handled. 37 00:03:13,300 --> 00:03:20,133 That is right from creating, installing, upgrading, roll back, deleting, status maintenance as well as version 38 00:03:20,133 --> 00:03:22,899 handling of the application and version handling 39 00:03:22,900 --> 00:03:29,100 It's going to be very simple with the helm where in a single command, I can roll back to the whatever 40 00:03:29,100 --> 00:03:35,000 version that I wanted as well as upgrading is also going to be using a single command. 41 00:03:35,000 --> 00:03:40,366 We will be seeing the entire lifecycle, as well as all the components that we have discussed over here 42 00:03:40,366 --> 00:03:43,032 in detail in future lectures.