Adopt the Helm Chart from the deprecated repository

[yonatankahana]

What is this PR

The latest official helm chart is in the old and deprecated repository and not currently being maintained. This chart uses very old image and soon (i hope) we will publish newer images and we will need to update the chart accordingly with the new features available (such as #20). To be ready for that we first need to bring it home.

Changes besides just copy and paste the old chart:

• Remove deprecation flag from the Chart.yaml
• Remove deprecation notices from README
• Update the Chart.yaml with the new project name and home URL
• Add kubeVersion semver range to Chart.yaml since the current version doesn't support v1.20 yet (Using Kubernetes v1.20.0, getting "unexpected error getting claim reference: selfLink was empty, can't make reference" #25)
• Bump the chart version
• Update READMEs with Helm3 examples and new chart location and installation instructions

Notice to reviewer

This PR consist of 2 commits, the first commit brings the chart AS-IS from the old repository, and the second commit shows my changes since then.
I did this to make the review process easier because most of the files not modified. Once we are ready to merge I will squash them into single commit if required.

[petermicuch]

@yonatankahana would it be possible to add helm index directly to this repo, so that people are still able to trigger helm install withouth the need to clone git repo itself? Or is there any plan to provide "add repo" support?

[yonatankahana]

@yonatankahana would it be possible to add helm index directly to this repo, so that people are still able to trigger helm install withouth the need to clone git repo itself? Or is there any plan to provide "add repo" support?

Yes, It it possible but not necessarily the best option, especially in the scope of this PR. My idea was to first bring it here and then, in a separate PR, we can automate the release process and consider where to host the packaged chart.
So the installation with git clone is not the final form of installation, but an intermediate stage.

[pierluigilenoci]

@wongma7 @jsafrane @kmova @jackielii @ashishranjan738 any of you have time to take a look? Thanks! ❤️

[immanuelfodor]

Would the migration from nfs-client-provisioner be as simple as remove the old and in with the new?

[yonatankahana]

Would the migration from nfs-client-provisioner be as simple as remove the old and in with the new?

yes.

[wongma7]

Yes, It it possible but not necessarily the best option, especially in the scope of this PR. My idea was to first bring it here and then, in a separate PR, we can automate the release process and consider where to host the packaged chart.
So the installation with git clone is not the final form of installation, but an intermediate stage.

I agree with this approach. In future it should be automated with github actions, for now at least the chart has to be imported into the repo.

[wongma7]

/lgtm

[pierluigilenoci]

@jsafrane @kmova could you please approve?

[kmova]

👍

[kmova]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kmova, yonatankahana

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 [kmova]

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