1 00:00:00,000 --> 00:00:12,866 Hi, Let us understand more about the public repository available as a part of Helm Hub and how to browse 2 00:00:12,866 --> 00:00:18,299 the charts available within the public repository and make use of the repository available from 3 00:00:18,300 --> 00:00:22,333 the helm hub to our local installation. 4 00:00:22,333 --> 00:00:26,999 Helm host the hub at this location hub.helm.sh 5 00:00:27,000 --> 00:00:34,500 where all the charts and the repositories are added, I can browse the list of charts available in public repository. 6 00:00:34,500 --> 00:00:38,733 over here and these are all the list of repositories and the charts within it. 7 00:00:38,733 --> 00:00:44,399 And since I have selected all, all the charts available in all the repositories will be displayed in 8 00:00:44,400 --> 00:00:49,800 case if I wanted to filter for the charts available within any specific repository, I can go ahead 9 00:00:49,800 --> 00:00:55,300 and do that. Here I do have the list of charts available as a part of stable repository. 10 00:00:55,300 --> 00:01:01,133 The same way I can browse the other repositories as well and through the helm client, I can 11 00:01:01,133 --> 00:01:02,466 browse the repositories. 12 00:01:02,466 --> 00:01:09,199 Also, if I get into the master node where I have installed helm client, I can provide the command helm. 13 00:01:09,200 --> 00:01:16,833 This is going to provide the help information as well as all the options that can be put in within the helm. Here 14 00:01:16,833 --> 00:01:22,799 One thing to be noted, the default value for the cache path, configuration path and the data path is available. 15 00:01:22,800 --> 00:01:29,300 Since this is a Linux system, it is available within the home directory.cache/helm 16 00:01:29,300 --> 00:01:32,433 If I want to change this, I can very well go ahead and change it. 17 00:01:32,433 --> 00:01:34,799 I am leaving all these values as default. 18 00:01:34,800 --> 00:01:40,900 The reason why I'm explaining about this specific environmental variable, because that's where the charts 19 00:01:40,900 --> 00:01:43,500 going to get stored. Now I can 20 00:01:43,500 --> 00:01:51,300 search the entire hub using the command helm search and then hub. 21 00:01:51,300 --> 00:01:55,200 So that's going to search all the charts available within the hub. 22 00:01:55,200 --> 00:02:01,133 thats the public repository location and it's going to list all the helm charts, their versions 23 00:02:01,133 --> 00:02:09,666 available within it, in case if I wanted to search for any specific chart, I can provide the command helm search hub. 24 00:02:09,666 --> 00:02:14,499 And if I wanted to search mysql chart, I can search mysql 25 00:02:14,500 --> 00:02:18,100 So it's going to list all the charts as a part of mysql 26 00:02:18,100 --> 00:02:20,933 or having the keyword mysql. 27 00:02:20,933 --> 00:02:23,899 Now I can search any specific repository 28 00:02:23,900 --> 00:02:34,066 Say, I wanted to search the repository stable helm search repo stable and I'm getting the error no 29 00:02:34,066 --> 00:02:35,999 repositories configured. The reason 30 00:02:36,000 --> 00:02:43,800 because in case if I want to search any specific repository, I need to configure the repository say where it is located. 31 00:02:43,800 --> 00:02:54,966 I can add the repository using the command repo, helm repo add I wanted to add the stable repository and provide the repository. 32 00:02:54,966 --> 00:03:02,899 url. Now I can list all the repositories available using the helm repo command list 33 00:03:02,900 --> 00:03:10,633 So I have the cache of the repository that is stable available over here and any chart that I wanted 34 00:03:10,633 --> 00:03:15,899 to add it's going to provide the information on how I can add this particular repository 35 00:03:15,900 --> 00:03:17,800 And the url corresponding to it. 36 00:03:17,800 --> 00:03:25,400 Stable is a very popular public repository where most of the stable charts are available as a part of the stable repository. 37 00:03:25,400 --> 00:03:32,533 Now I can search the repository stable and look for the charts available within it. 38 00:03:32,533 --> 00:03:35,966 helm search repo stable. 39 00:03:35,966 --> 00:03:38,666 So I'm going to search the repository stable. 40 00:03:38,666 --> 00:03:41,532 So I do have the list of charts 41 00:03:41,533 --> 00:03:43,533 And their versions within it. 42 00:03:43,533 --> 00:03:48,133 So it's going to list the chart version and the application version within it. 43 00:03:48,133 --> 00:03:56,266 Say if I wanted to search for mysql chart within stable repository, I can use the command helm search 44 00:03:56,266 --> 00:03:58,432 repo I wanted to search a stable. 45 00:03:58,433 --> 00:04:01,833 Within that, I wanted to search for mysql 46 00:04:01,833 --> 00:04:06,066 So it's going to list all the charts with the keyword mysql 47 00:04:06,066 --> 00:04:08,699 And the chart version and the application version. 48 00:04:08,700 --> 00:04:14,566 In this case, I have two records mysql and mysql dump with the corresponding chart version and 49 00:04:14,566 --> 00:04:17,031 the application version. 50 00:04:17,033 --> 00:04:22,533 The same thing can be browsed within the hub as well. For example, if I get into the stable, I 51 00:04:22,533 --> 00:04:27,333 can search for the chart, mysql. And within the mysql 52 00:04:27,333 --> 00:04:34,933 We will be having the clear instruction on how to add this particular repository as a part of our installation. 53 00:04:34,933 --> 00:04:41,666 Here I do have the instruction on the installation chart, as we discussed in the beginning, the repositories 54 00:04:41,666 --> 00:04:46,599 that we are adding will get stored as a part of the configuration location. 55 00:04:46,600 --> 00:04:53,400 If I provide the help command, here I will be in a position to find where the cache will be stored. 56 00:04:53,400 --> 00:04:59,966 So in this case, Linux system, it's going to get stored within the home directory.cache/helm 57 00:04:59,966 --> 00:05:05,232 I can get into that specific location. Here I can search for the directories 58 00:05:05,233 --> 00:05:07,566 I will be having a repository. Here 59 00:05:07,566 --> 00:05:10,799 All the repositories will be available, in my case 60 00:05:10,800 --> 00:05:16,933 I have these repositories because earlier it was added and I can go ahead and refresh this particular 61 00:05:16,933 --> 00:05:21,799 repository or import the latest version from the helm hub. 62 00:05:21,800 --> 00:05:26,000 The location of this particular chart cache is for informational purpose. 63 00:05:26,000 --> 00:05:29,966 We are not going to change the files available over here directly. 64 00:05:29,966 --> 00:05:38,299 I'll explain the detailed way of how to update the values and provide the updated values to the chart in the future lecture. 65 00:05:38,300 --> 00:05:43,566 So in a quick summary, we have seen how to browse the charts within the public repository 66 00:05:43,566 --> 00:05:50,499 As a part of Helm Hub and how to add a repository within the helm client and browse the charts 67 00:05:50,500 --> 00:05:52,766 available within the repository. 68 00:05:52,766 --> 00:05:55,966 Don't worry about the terminologies. Few of the terminologies 69 00:05:55,966 --> 00:05:59,066 We will be connecting the dots in future lecture. 70 00:05:59,066 --> 00:06:05,632 This is a quick introduction so that we can get started quickly and create our own chart and deploy it within the cluster.