1 00:00:00,000 --> 00:00:08,866 Hi, Let us understand how to do the installation of helm. 2 00:00:08,866 --> 00:00:15,166 Helm is available as a binary file where the tar file can be downloaded and it can be extracted. 3 00:00:15,166 --> 00:00:22,499 And once it is added into the binary directory, it can be directly executed. Before getting into the installation 4 00:00:22,500 --> 00:00:28,000 We need to have an understanding of the helm architecture as well as the major difference between version 5 00:00:28,000 --> 00:00:31,133 two and version three. As a part of this particular course 6 00:00:31,133 --> 00:00:33,466 We are going to discuss about version 3 7 00:00:33,466 --> 00:00:36,999 But still understanding of version two is important. 8 00:00:37,000 --> 00:00:40,600 First, let's understand how version two was designed where 9 00:00:40,600 --> 00:00:49,033 Once the helm is installed, say I do have helm over here and the user can interact with the helm 10 00:00:49,033 --> 00:00:56,099 and within the kubernetes cluster where I am going to use the helm I need to install a service called tiller 11 00:00:56,100 --> 00:01:03,400 service and all the interaction between the helm and to the kubernetes cluster will be happening through 12 00:01:03,400 --> 00:01:09,200 this particular tiller service and within the kubernetes cluster 13 00:01:09,200 --> 00:01:15,466 The tiller service will be getting executed and the communication will happen only between Helm and 14 00:01:15,466 --> 00:01:21,799 the tiller service and tiller service will take care of deploying various components within the kubernetes cluster. 15 00:01:21,800 --> 00:01:25,833 As per the charts available within the repository. 16 00:01:25,833 --> 00:01:28,533 So I'll be having the repository. 17 00:01:28,533 --> 00:01:33,399 And from here, I will be getting different charts. 18 00:01:33,400 --> 00:01:36,866 This charts will be used by the helm 19 00:01:36,866 --> 00:01:40,632 This is in version two, and in version three 20 00:01:40,633 --> 00:01:43,499 There was a major change where this particular tiller 21 00:01:43,500 --> 00:01:46,066 service was remote. 22 00:01:46,066 --> 00:01:51,432 And the helm will be interacting with the kubernetes cluster directly and the access will be provided 23 00:01:51,433 --> 00:01:54,466 using role based access control. 24 00:01:54,466 --> 00:02:02,132 So once if I have the kubernetes cluster and have access to any client like helm, I can use the helm to 25 00:02:02,133 --> 00:02:03,833 deploy any service within the kubernetes 26 00:02:03,833 --> 00:02:10,333 cluster and I can use the chart and deploy the entire application into the kubernetes cluster. 27 00:02:10,333 --> 00:02:14,599 So this is a major change in version three. 28 00:02:14,600 --> 00:02:19,300 So the one that we are going to see as a part of this particular course is helm version three, where 29 00:02:19,300 --> 00:02:21,866 I need to install only this helm client 30 00:02:21,866 --> 00:02:28,599 And that is available as a binary file and the entire binary file will be available within this specific location. 31 00:02:28,600 --> 00:02:36,700 I can choose whatever the version that is available. As a part of this particular recording, the version 3.2.1 is the latest one. 32 00:02:36,700 --> 00:02:42,966 So I can download from this specific location and the binary is divided for various platforms, whatever 33 00:02:42,966 --> 00:02:44,532 the platform that we wanted 34 00:02:44,533 --> 00:02:46,999 We can download and install over here. 35 00:02:47,000 --> 00:02:49,000 All I need is copy the url. 36 00:02:49,000 --> 00:02:52,633 And the one that I have is a kubernetes cluster. 37 00:02:52,633 --> 00:02:57,133 And I'm going to use the master machine as the client. 38 00:02:57,133 --> 00:03:02,099 So before doing the installation, I need to have a quick understanding on the kubernetes cluster architecture 39 00:03:02,100 --> 00:03:07,833 as well where I do have a master and three worker machines. 40 00:03:07,833 --> 00:03:10,833 In case if you doesn't have any access to the cluster 41 00:03:10,833 --> 00:03:13,366 You can go ahead and do the installation of minikube 42 00:03:13,366 --> 00:03:15,532 how to do the installation of minikube 43 00:03:15,533 --> 00:03:18,099 and the instruction to do the setup 44 00:03:18,100 --> 00:03:23,733 I have provided as a part of a lecture at the end of this specific course you can refer to that. 45 00:03:23,733 --> 00:03:29,466 And once the access to the cluster is available, you can make use of it and the client can be installed 46 00:03:29,466 --> 00:03:36,099 in any location. And to get started quickly, I have installed the helm as a part of the master machine. 47 00:03:36,100 --> 00:03:41,866 So once the helm is installed, it can directly interact with the kubectl commands as a part of 48 00:03:41,866 --> 00:03:46,332 the master. So within the master machine that is available over here 49 00:03:46,333 --> 00:03:52,099 So this is the master machine where it is marked with node 2 and node 3, node 4 and node 1 50 00:03:52,100 --> 00:03:54,966 are the worker machines within the master 51 00:03:54,966 --> 00:04:04,299 I can download the helm using the command wget and then the link over here 52 00:04:04,300 --> 00:04:06,400 So the download should be available. 53 00:04:06,400 --> 00:04:14,233 And once the download is available, I can extract this particular download using the command provided that is 54 00:04:14,233 --> 00:04:16,099 tar - xvf 55 00:04:16,100 --> 00:04:18,833 And then extract this specific file. 56 00:04:18,833 --> 00:04:26,933 Once the file is extracted, the helm executable will be available as a part of the Linux A and B slash helm 57 00:04:26,933 --> 00:04:31,766 I do have the tar file. Let me go ahead and extract this specific file. 58 00:04:31,766 --> 00:04:39,632 tar - zxvf and then the file name. 59 00:04:39,633 --> 00:04:41,499 So the file will get extracted. 60 00:04:41,500 --> 00:04:45,033 And within this specific folder, I should have the helm executable 61 00:04:45,033 --> 00:04:47,999 I can move this specific file as a part of the 62 00:04:48,000 --> 00:04:55,500 bin available so that I can execute the helm, command from any location. 63 00:04:55,500 --> 00:05:09,733 So I can use the command move the helm executable into the local bin helm 64 00:05:09,733 --> 00:05:14,133 I'm getting this warning because already helm is existing over here. 65 00:05:14,133 --> 00:05:22,033 I can go ahead and over write and I can provide the command helm from any location. 66 00:05:22,033 --> 00:05:28,433 Once if I get the instructions for helm, that means the installation of helm is working fine. 67 00:05:28,433 --> 00:05:32,999 So in a quick summary we have seen how to do the installation as well as the architectural difference between 68 00:05:33,000 --> 00:05:40,233 version two and version three and in version three installation of helm client is sufficient enough 69 00:05:40,233 --> 00:05:44,266 And this particular helm client should have access to the kubernetes cluster. 70 00:05:44,266 --> 00:05:50,899 In our case, we did the installation as a part of the master itself so directly it can have the access. 71 00:05:50,900 --> 00:05:55,600 In future lectures I will demonstrate how to use the helm with the minikube as well.