[stable/nfs-server-provisioner] deprecating chart

[mattfarina]

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

• fixes #

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• DCO signed
• Chart Version bumped
• Variables are documented in the README.md
• Title of the PR starts with chart name (e.g. [stable/mychartname])

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mattfarina

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:

• stable/nfs-server-provisioner/OWNERS [mattfarina]

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

[scottrigby]

See #24310

[nagasitaramthigulla]

since stable/nfs-server-provisioner is deprecated
do we have any alternative for this we can use

[kvaps]

Hey, there was another PR #23891

With the link to the new repository
https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner

[scottrigby]

(deleted duplicate comment)

@kvaps sorry we missed your earlier PR. By the time we needed to turn down the stable and incubator repos, we had to do this programmatically for several hundred charts. We'll want to update https://github.com/helm/charts/issues/21103 to reflect the new home (see this comment https://github.com/helm/charts/issues/21103#issuecomment-732992002 a format for updating that issue after the repo became read-only still has to be set up)