Hi. Now let us create another chart and add it as a part of the repository
And understand how repository can handle multiple charts.
Let me go ahead and create a new chart helm create myrepo2
So I should have another folder myrepo2 as a part of the location where I created the chart.
Let me get into the folder.
Let me go ahead and modify the chart.yaml file
Now, I'm going to package this particular chart using the package command helm package myrepo2
So accordingly it's going to create the zipped content so that should be available over here.
Now, let's understand what happens if I copy this particular zip file into the repository storage.
As I mentioned earlier, the storage could be a GitHub
or Amazon S3 bucket or even any other cloud storage.
In this case it's a local storage
So I can move this particular file using FTP or some other option.
Since the Chart Museum repository running in the same machine
I can use the copy command.
So I'm going to copy this particular zipped content into the location where the Chart Museum is pointing to for the storage.
Now, if I check this particular folder location I should have this particular zipped content as well.
So I do have it, now let me go ahead and update the repository.
Now, let me search repository.
Now, I do have the other chart as well.
That is myrepo2 as a part of the other chart.
This is the chart that we had added manually by
Copying the file into the storage location. In case if I wanted to list all the version as we discussed earlier
I can use the flag -l, where it is going to list all the available version.
So if you observe very carefully, we do have two version for this particular chart
repo test and I do have another chart and only one version is available.
So this is a quick demo on how I can manage multiple charts
And another way of copying the chart package into the storage location and automatically chart museum
going to pick this and make it available for the helm clients.