1 00:00:00,000 --> 00:00:05,600 Hi 2 00:00:05,600 --> 00:00:12,766 Let us understand how to install a chart once the repository is configured with the client. In our installation 3 00:00:12,766 --> 00:00:14,932 We do have the stable repository. 4 00:00:14,933 --> 00:00:16,833 I can list the repositories available. 5 00:00:16,833 --> 00:00:20,699 Helm repo list 6 00:00:20,700 --> 00:00:28,433 So I do have one repository that is stable and this is the url from where it is going to pick the charts. 7 00:00:28,433 --> 00:00:30,566 And this url is a constant one. 8 00:00:30,566 --> 00:00:36,066 We can get this from the helm documentation as well and all the commands that I'm executing 9 00:00:36,066 --> 00:00:41,532 I will be adding it as a part of the resources so that you can download the resource from the corresponding 10 00:00:41,533 --> 00:00:43,566 lecture and execute the commands 11 00:00:43,566 --> 00:00:45,832 Real easy and quickly. 12 00:00:45,833 --> 00:00:50,866 Now, let me go ahead and update this particular repository so that any future charts available 13 00:00:50,866 --> 00:00:56,366 as a part of this particular repository will get added and get cached within this particular client 14 00:00:56,366 --> 00:01:02,832 location helm repo update 15 00:01:02,833 --> 00:01:07,333 So it's going to be called the latest information, and update the cache. 16 00:01:07,333 --> 00:01:10,033 All the charts are off. Latest one now. 17 00:01:10,033 --> 00:01:21,199 Now I can go ahead and search for the repository say mysql, helm search repo stable/mysql 18 00:01:21,200 --> 00:01:28,166 So I do have the chart and that's going to use the version 5.7.30 of mysql 19 00:01:28,166 --> 00:01:32,199 Let me go ahead and do the installation of this particular latest version. 20 00:01:32,200 --> 00:01:37,366 In case if I wanted any specific version, I can go ahead and do the installation. To get started quickly 21 00:01:37,366 --> 00:01:47,666 I'm going to use the stable and latest version helm install stable/mysql and I will request 22 00:01:47,666 --> 00:01:52,232 helm to generate a name for this particular installation. 23 00:01:52,233 --> 00:01:54,799 Generate name 24 00:01:54,800 --> 00:01:55,800 The installation is done. 25 00:01:55,800 --> 00:02:01,666 and it is going to provide the nodes in terms of how to access the mysql that is getting deployed within 26 00:02:01,666 --> 00:02:07,332 the kubernetes cluster and how I can test this particular mysql installation. 27 00:02:07,333 --> 00:02:12,233 And in the same machine I do have the kubernetes client installation that is kubectl 28 00:02:12,233 --> 00:02:20,099 I can check the entities that got deployed as a part of this specific cluster kubectl get all 29 00:02:20,100 --> 00:02:24,433 Please make yourself comfortable with the basics of kubernetes commands. 30 00:02:24,433 --> 00:02:31,666 And in case, if you wanted a revision, you can verify the other course I have posted related to kubernetes 31 00:02:31,666 --> 00:02:34,032 So this particular chart deployed a pod 32 00:02:34,033 --> 00:02:37,699 and the service mysql 33 00:02:37,700 --> 00:02:41,733 And a deployment, so automatically it configured the replica set 34 00:02:41,733 --> 00:02:44,699 deployment, service and the pod. For the time being 35 00:02:44,700 --> 00:02:47,100 Let's not worry about this particular details from where 36 00:02:47,100 --> 00:02:52,733 these details are configured and how the details will be provided to the kubernetes. 37 00:02:52,733 --> 00:03:05,266 The same way let me go ahead and do another installation helm install stable/airflow 38 00:03:05,266 --> 00:03:12,232 And let me give a name to it, myairflow 39 00:03:12,233 --> 00:03:20,766 In the earlier command we asked the helm to generate a name, this time I'm giving my own name for this particular chart 40 00:03:20,766 --> 00:03:23,332 For the time being, let's not worry about this particular chart 41 00:03:23,333 --> 00:03:26,999 What it does and get into the details of this particular chart 42 00:03:27,000 --> 00:03:31,766 So it's going to provide information on how this particular entity is getting deployed within the cluster 43 00:03:31,766 --> 00:03:33,232 and how to access them. 44 00:03:33,233 --> 00:03:41,399 I can get the details about these parts and services using the kubectl command get all 45 00:03:41,400 --> 00:03:45,166 So all the required pods 46 00:03:45,166 --> 00:03:54,766 Services, deployment, replica set everything got deployed and all the required information will be available. 47 00:03:54,766 --> 00:04:00,132 So basically, the charts, it's going to facilitate deploying various components of kunernetes 48 00:04:00,133 --> 00:04:06,599 And in one single go, using a single command, we can deploy the entire infrastructure that is required 49 00:04:06,600 --> 00:04:10,266 for the application to be up and running within kubernetes 50 00:04:10,266 --> 00:04:18,399 And I can list what are all the charts that got deployed helm ls 51 00:04:18,399 --> 00:04:20,866 here we have 2 charts myairflow 52 00:04:20,866 --> 00:04:23,199 And what's the version 53 00:04:23,200 --> 00:04:27,300 And what is the revision currently one revision and 54 00:04:27,300 --> 00:04:28,500 The application version. 55 00:04:28,500 --> 00:04:34,066 Those informations will be available now in case if I wanted to delete any specific chart, I can 56 00:04:34,066 --> 00:04:34,932 go ahead and do that. 57 00:04:34,933 --> 00:04:43,533 Let me delete one helm and install myairflow so all the 58 00:04:43,533 --> 00:04:48,366 entities related to this particular chart will be removed from the kubernetes cluster as well. 59 00:04:48,366 --> 00:04:55,332 So the last one it is getting terminated so all the parts related to that specific chart got terminated. 60 00:04:55,333 --> 00:05:02,066 This is a quick demonstration on how to use the charts and deploy the entities into the kubernetes and 61 00:05:02,066 --> 00:05:04,632 to have a quick revision on kubernetes 62 00:05:04,633 --> 00:05:08,633 And the related components I have added the lecture at the end of this particular course. 63 00:05:08,633 --> 00:05:10,333 You can very well refer to them. 64 00:05:10,333 --> 00:05:14,799 And if you want a detailed understanding on the kubernetes, you can refer to my other course that I 65 00:05:14,800 --> 00:05:17,666 have posted related to the kubernetes 66 00:05:17,666 --> 00:05:22,766 So in a quick summary, we have seen how to import the repositories, how to verify the charts within 67 00:05:22,766 --> 00:05:31,799 the repository and use a chart and do a quick release into the kubernetes cluster using the helm install command. 68 00:05:31,800 --> 00:05:35,166 Again, let me remind you all this is a quick introduction 69 00:05:35,166 --> 00:05:38,966 We are going to have detailed discussion on each and every command 70 00:05:38,966 --> 00:05:41,066 And their syntax in the future lecture.