1 00:00:00,000 --> 00:00:11,366 Hi, Let us understand how to do the installation of helm and connect with minikube to test with chart 2 00:00:11,366 --> 00:00:14,499 deployments. Already we did the installation of minikube 3 00:00:14,500 --> 00:00:18,733 and saw how to start the minikube and check the status. 4 00:00:18,733 --> 00:00:22,433 Now let us go ahead and do the installation of helm 5 00:00:22,433 --> 00:00:24,466 Let me go ahead and open another power shell. 6 00:00:24,466 --> 00:00:28,966 The dashboard is running over here and check the status of minikube 7 00:00:28,966 --> 00:00:34,532 with the command minikube status, the host is running. 8 00:00:34,533 --> 00:00:40,366 kubelet is also running, API server is also running and kubeconfig is also configured. 9 00:00:40,366 --> 00:00:43,399 So I can make use of this minikube installation. 10 00:00:43,400 --> 00:00:49,166 Now lets understand how to do the installation of helm. When it comes to the installation of helm 11 00:00:49,166 --> 00:00:50,366 There are two major versions. 12 00:00:50,366 --> 00:00:56,266 That is version two and version three. Within helm quickstart guide page here 13 00:00:56,266 --> 00:01:01,566 I do have the instruction on how to do the installation, the binary can be downloaded from this specific 14 00:01:01,566 --> 00:01:05,498 location. As a part of the official releases 15 00:01:05,500 --> 00:01:10,066 We will be having releases for both version two and version three. 16 00:01:10,066 --> 00:01:12,932 So this is for version three at the same time 17 00:01:12,933 --> 00:01:17,699 we will have the releases for version two as well. 18 00:01:17,700 --> 00:01:23,966 So please be careful when you are downloading. In this particular course we are using version three. 19 00:01:23,966 --> 00:01:30,766 So if you download version two, you will have the tiller server as well and I'm going to download version three 20 00:01:30,766 --> 00:01:33,799 that will be available as a zip file for Windows. 21 00:01:33,800 --> 00:01:42,000 Once this is downloaded, I can extract enough folder, say for example, here I do have the downloads for version three. 22 00:01:42,000 --> 00:01:48,600 Within that I will be having the helm executable, this needs to be executed within the command prompt. 23 00:01:48,600 --> 00:01:54,400 And in case if you download version two, you will have the executable for tiller server as well. You need to 24 00:01:54,400 --> 00:02:01,066 to start tiller server as well and configure the tiller server to get that executed within the kubernetes 25 00:02:01,066 --> 00:02:03,566 cluster. As this is a old version 26 00:02:03,566 --> 00:02:05,466 Let's not worry about this. 27 00:02:05,466 --> 00:02:11,332 Let's get into the version 3 and I need to execute this particular executable and it needs to get executed 28 00:02:11,333 --> 00:02:17,733 within the command prompt, so I can execute the command helm or what I can do 29 00:02:17,733 --> 00:02:22,399 I can add this particular path as a part of the system environmental variable 30 00:02:22,400 --> 00:02:29,366 path. So within system properties advanced settings environmental variables 31 00:02:29,366 --> 00:02:38,499 within path. I do have the version 3 added as a part of the path so I can execute the helm command from any location. 32 00:02:38,500 --> 00:02:44,700 I'm going to use this specific folder to create the charts and here I should be in a position to execute 33 00:02:44,700 --> 00:02:51,766 helm command and it'll understand provide the help message that means helm configuration is well and good. 34 00:02:51,766 --> 00:02:55,299 Let me go ahead and create a chart and deploy that within the minikube 35 00:02:55,300 --> 00:02:59,633 The details about how to do the chart creation 36 00:02:59,633 --> 00:03:02,199 Everything we have discussed in a separate lecture. 37 00:03:02,200 --> 00:03:04,166 This is a quick test on 38 00:03:04,166 --> 00:03:07,966 whether the configuration and installation is good or not. 39 00:03:07,966 --> 00:03:15,499 Let me go ahead and create a chart helm create mychart, so it will create mychart. 40 00:03:15,500 --> 00:03:17,966 So I do have mychart as a folder. 41 00:03:17,966 --> 00:03:21,299 Let me go ahead and install mychart within 42 00:03:21,300 --> 00:03:23,200 minikube and by default minikube 43 00:03:23,200 --> 00:03:28,900 is configured so automatically it's going to connect to the minikube because kubectl is configured to 44 00:03:28,900 --> 00:03:30,466 interact with API 45 00:03:30,466 --> 00:03:42,799 server of minikube. Let me do the installation helm install and name of the installation./mychart. Go ahead and do the installation. 46 00:03:42,800 --> 00:03:47,800 Now I can get whether all the components deployed within the kubernetes or not using kubectl 47 00:03:47,800 --> 00:03:53,966 command kubectl get all. So it deployed a pod 48 00:03:53,966 --> 00:04:00,232 And I should be in a position to check the list of deployments using helm list 49 00:04:00,233 --> 00:04:02,333 Yes, it is deployed. 50 00:04:02,333 --> 00:04:04,566 Let me get into the dashboard and check the status. 51 00:04:04,566 --> 00:04:07,066 I can get the list of pods. 52 00:04:07,066 --> 00:04:10,332 So I should have the pod for the chart as well. 53 00:04:10,333 --> 00:04:12,133 Yes, I do have a pod 54 00:04:12,133 --> 00:04:18,599 And that got deployed 47 seconds ago, the same way I can deploy anything that I wanted. 55 00:04:18,600 --> 00:04:24,466 And within this specific course, we discussed in detail about how to work with various environments 56 00:04:24,466 --> 00:04:30,932 charts. So this confirms the configuration of helm is well and good. 57 00:04:30,933 --> 00:04:34,033 Now let's say how to uninstall this helm installation. 58 00:04:34,033 --> 00:04:41,899 I can issue the command helm uninstall and name of the installation. 59 00:04:41,900 --> 00:04:49,000 minikube test. So it should remove the pod. 60 00:04:49,000 --> 00:04:53,800 That was deployed as a part of this specific helm installation. 61 00:04:53,800 --> 00:04:56,533 There are no pods. It is removed. 62 00:04:56,533 --> 00:05:04,933 Now let's stop the minikube, minikube stop 63 00:05:04,933 --> 00:05:09,133 So it should stop the virtual pulse corresponding to the minikube 64 00:05:09,133 --> 00:05:11,399 And the system should be clean. 65 00:05:11,400 --> 00:05:19,033 So in a quick summary we saw how to do the installation of helm and connect with minikube and try out the chart deployments.