Hi, Now, I do have the GitHub repository with the chart package and index.yaml file
And that is committed and it is visible over here.
Now, I am going to use this specific GitHub repository and create a chart package, install them and
test it out. If I get into the readme.md file
I do have an option to visualize this as a raw format and without that specific file I can get
the raw folder location. This is what I'm going to use it as a repo
url. Now, I'm going to add the repo.
Let me list the repos available helm repo list. I do have two repo
Now, I'm going to add this specific repo as well
Let me go ahead and add the repo. I'll use the command helm repo add
And I can pass the username and password.
with the options --username and --password
repo add and I'll provide the user name.
I'll add the user name over here --password.
I'll mention the access token then name of the repository and the repo link. So repo link will get added.
I can list the repos and the new repo that got added that will also be visible.
Now, I can search the charts available within this specific repo using the common helm search repo
And then name of the repo. yes, I do have one chart that we created and added as a part of the Github repository.
Now I can go ahead and add any number of charts into the repository and every time whenever I am
adding it, I need to update the index.yaml file. So for quick demo
Let me go ahead and create another chart with the name getrepotest2
So this is the folder location. I'm going to do the package.
Here I am going to do the package, helm package and then the repository path.
So a new file will get created. So this is what the new file that got created.
Now I need to update the index file so I'll use the command helm repo index dot
So the index file will get updated. Here I do have two entries for the two repositories.
Now these two files needs to added into the github repository.
I can use the command git add so that it will get added to the local repository.
commit them with the message. So two files got added and I'm going to push this into the master.
If I push it the new changed charts will also get added.
Let me provide the user name and the token.
Now let me go ahead and verify the github page.
I do have 2 charts and the index.yaml file should have 2 entries.
Now I can go ahead and do the update of the repository over here helm repo update
So it's going to connect to the repositories and check
Is there any update if yes, it's going to keep itself up to date with the local cache after update
I can search the repository and I should have 2 charts within it.
Yes, I do have 2 charts gitrepotest and gitrepotest2, now I can make use of any of this charts and
do the deployment of kubernetes resources.
Now, let me go ahead and clean up the
GitHub repository. As a part of the GitHub repository if you get into the settings
developer settings personal access token. I do have 2 access token in case if you feel the access
token was compromised for some reason you can go ahead and regenerate the token. A new token
will be issued and we can start using the new token.
And if the purpose of that specific token is done, we can go ahead and delete them as well
If you remember within the demo I used the token of this particular access token as well
So I will be regenerating it for my future use. So in a quick summary
We have seen how to add the repository
url from the GitHub and do the update as well as add more charts into the existing repository
and search for the repository after doing the update.