1 00:00:00,000 --> 00:00:07,566 Hi, Let us have little more details about Chart Repositories. 2 00:00:07,566 --> 00:00:16,099 It's nothing but a simple HTTP server which can host a set of files like index.yaml file and other chart packages. 3 00:00:16,100 --> 00:00:22,200 And based on the get request, it can serve those index.html and the chart packages 4 00:00:22,200 --> 00:00:24,766 and the clients like helm client or other 5 00:00:24,766 --> 00:00:31,266 CICD tools can pull this charts from this server and make use of them. When the charts are ready 6 00:00:31,266 --> 00:00:36,899 I can upload these into the server that is index.yaml file and the chart packages. Chart package is nothing but 7 00:00:36,900 --> 00:00:40,633 the entire chart folder and the index.yaml file 8 00:00:40,633 --> 00:00:46,433 index.yaml file is nothing but that's going to be the index on what are all the charts 9 00:00:46,433 --> 00:00:48,899 available and what versions available 10 00:00:48,900 --> 00:00:55,100 This is going to look somewhat similar to this where I can have n number of entries and what are all the 11 00:00:55,100 --> 00:00:57,066 charts available when it was created 12 00:00:57,066 --> 00:01:02,332 Description about it , the digest to understand what versios being managed 13 00:01:02,333 --> 00:01:05,199 Name and source different informations 14 00:01:05,200 --> 00:01:06,833 And I can have multiple versions 15 00:01:06,833 --> 00:01:15,333 as well. Say for example, in this particular case I do have the version 0.2 and the same entry is available as 0.1 16 00:01:15,333 --> 00:01:19,133 So I can have multiple entries for a chart and the similar way 17 00:01:19,133 --> 00:01:21,133 I can have multiple charts as well. 18 00:01:21,133 --> 00:01:25,299 In this case, I do have charts for Alpine as well as nginx. 19 00:01:25,300 --> 00:01:31,133 This looks very similar to the registry management within the OCI registry or any other source 20 00:01:31,133 --> 00:01:33,966 control system. This is how the configurations will be. 21 00:01:33,966 --> 00:01:40,132 I can have n number of packages and the index.yaml file within the charts folder and that particular 22 00:01:40,133 --> 00:01:44,733 charts folder should be available as a part of some Web server dock root 23 00:01:44,733 --> 00:01:49,066 or it can be hosted as a part of Google Compute Cloud Buckets or AWS 24 00:01:49,066 --> 00:01:56,199 S3 buckets or GitHub pages and we can have our own web server or there is a dedicated server to host the 25 00:01:56,200 --> 00:01:58,866 chart repositories that is chart museum. 26 00:01:58,866 --> 00:02:03,532 We will be having detailed discussion on Chart Museum on how to install, how to configure the 27 00:02:03,533 --> 00:02:05,833 repository within it and make use of it 28 00:02:05,833 --> 00:02:11,699 And we will see a couple of options by using either AWS S3 bucket or GitHub pages. 29 00:02:11,700 --> 00:02:16,266 That's a very simple configuration where I can add the bucket and make use of it. 30 00:02:16,266 --> 00:02:23,199 And once the repository is created, I can use the helm client to push my own chart and see what are 31 00:02:23,200 --> 00:02:29,000 all the versions being managed and pull whatever the version that is required from the particular repository 32 00:02:29,000 --> 00:02:31,466 I can pull it and make use of it. 33 00:02:31,466 --> 00:02:36,966 So the first thing, what I am going to do, I am going to install my own server that is using chart 34 00:02:36,966 --> 00:02:42,432 museum and create a repository and add my own charts within it. 35 00:02:42,433 --> 00:02:44,266 Chart museum is available over here. 36 00:02:44,266 --> 00:02:49,399 This is dedicatedly made to manage the charts and host the chart repositories. 37 00:02:49,400 --> 00:02:52,000 I can do the installation. In the next lecture 38 00:02:52,000 --> 00:02:56,866 We are going to have detailed instructions on how to do the installation and run the chart repository. 39 00:02:56,866 --> 00:03:00,066 And add our own chart within the repository.