1
00:00:00,000 --> 00:00:08,500
Hi, Let us understand about chart repositories. Within the workflow of charts

2
00:00:08,500 --> 00:00:14,100
we will come across this terminologies that is repositories and registries a lot.

3
00:00:14,100 --> 00:00:20,300
Let us have a quick overview on what role it's going to play and where it's going to come into picture

4
00:00:20,300 --> 00:00:25,633
within the workflow of the chart. Before getting into the details about the chart repositories

5
00:00:25,633 --> 00:00:30,233
Let's understand the workflow, assume I do  have n number of charts. Already

6
00:00:30,233 --> 00:00:35,899
We discussed how to create the charts and various building blocks of the charts and using those building

7
00:00:35,900 --> 00:00:42,200
blocks assume I do have n number of charts and those charts needs to be kept in a centralized location

8
00:00:42,200 --> 00:00:47,733
so that the other tools, like CICD tools or other developers can make use of it.

9
00:00:47,733 --> 00:00:55,333
And that particular centralized location we call that as a repository or registry. Registry is OCI compatable

10
00:00:55,333 --> 00:00:59,999
That is open container and image standard registry.

11
00:01:00,000 --> 00:01:03,833
And that's what it's going to be followed within the docker.

12
00:01:03,833 --> 00:01:09,933
I can manage the charts within the registry as well as I can have my own repository as well.

13
00:01:09,933 --> 00:01:16,399
The traditional way of doing is using the repository and nowadays OCI registry is also supported.

14
00:01:16,400 --> 00:01:23,766
We are going to see the demo for both these options and once I do have the charts within the registry or repository,

15
00:01:23,766 --> 00:01:31,466
I can manage versions, maintain versions and pull whatever the version that is required and give permissions

16
00:01:31,466 --> 00:01:33,232
so all such control we can do.

17
00:01:33,233 --> 00:01:38,766
You can visualize registry or repository as a source control system where the charts will be managed

18
00:01:38,766 --> 00:01:46,132
within it and shared across the users and CICD tool or development tool will come into picture where it can

19
00:01:46,133 --> 00:01:50,799
pull the chart it needs and deploy it into the Kubernetes cluster.

20
00:01:50,800 --> 00:01:56,966
This is how general workflow looks like, how the charts would get deployed into the kubernetes cluster.

21
00:01:56,966 --> 00:02:02,466
And this particular section, we are going to have detailed discussion about how to set up our own repository

22
00:02:02,466 --> 00:02:10,066
as well as use GitHub pages or Amazon Cloud for hosting the repository and make use of different

23
00:02:10,066 --> 00:02:13,999
versions of the charts within the repository using the demo.

24
00:02:14,000 --> 00:02:20,100
Along with that, we will see how to use the registry as well. For that I will be hosting a Docker registry

25
00:02:20,100 --> 00:02:26,433
and add the charts within it and make use of managing the versions within the registry as well.

26
00:02:26,433 --> 00:02:32,199
So this particular section, we're going to concentrate more on this particular area where how to set

27
00:02:32,200 --> 00:02:37,600
up our own repository, manage those repositories and add the charts within them,

28
00:02:37,600 --> 00:02:40,866
How to visualize, what are all the versions available within it

29
00:02:40,866 --> 00:02:42,932
What are the charts available within it

30
00:02:42,933 --> 00:02:48,399
Basically, the entire chart management within the repository we are going to do in this particular section.