added helm repo yaml in docs folder

[kferrone]

This will allow helm to add the public docs of this git repo as a helm
repo. The helm tar packages are actually stored in git releases still.

Is this a bug fix or adding new feature?
A new feature as this repo did not have a public helm repo and required installing the charts tar.gz directly.

What is this PR about? / Why do we need it?
Not all ways of using helm will allow you to install a chart from a url. Installing charts from a repo always works. For example if you are using FluxCD Helm Operator or AWS CDK, they do not support installing from url directly without a specific repo. . . as far as I know.

What testing is done?
I have done this before. I can't directly test this repo until the docs folder is made public.

As long as the docs folder is public on Github Pages then the following command would work:

helm repo add aws-efs https://kubernetes-sigs.github.io/aws-efs-csi-driver
helm upgrade -i aws-efs-csi-driver aws-efs/aws-efs-csi-driver --namespace kube-system

I made this exact repo available on my account to test out.
Add the repo

helm repo add aws-efs https://kferrone.github.io/aws-efs-csi-driver

Search the repo:

helm search repo aws-efs

which should display:

NAME                            CHART VERSION   APP VERSION     DESCRIPTION                        
aws-efs/aws-efs-csi-driver      0.1.0           0.3.0           A Helm chart for AWS EFS CSI Driver

Now try a pull and see the download:

helm pull aws-efs/aws-efs-csi-driver

Fixes: #146

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @kferrone!

It looks like this is your first PR to kubernetes-sigs/aws-efs-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/aws-efs-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @kferrone. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kferrone]

I signed it

[leakingtapan]

/ok-to-test

[leakingtapan]

Thx for creating the helm index! I will move the file to github page in a separate branch and make it public once this is merged.

[leakingtapan]

Just created gh-pages branch, please create the index in that branch at project root and update the helm install section in README

[leakingtapan]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kferrone, leakingtapan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [leakingtapan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jqmichael]

Thx for creating the helm index! I will move the file to github page in a separate branch and make it public once this is merged.

Just curious, what's the benefit of using a separate branch vs keeping it at master?