support multiple (many) namespaces

[therc]

This is a continuation, more or less, of issue 1210 in the old repo.
I even had a PR that implements what is described here:
kubernetes-retired/external-storage#1210 (comment)

Basically, if you need to export the same NFS mount to a large number of namespaces, now you would do this:

1. create a PVC for the mount, using whatever NFS provisioner you want
2. run a second NFS provisioner in the new alias mode. It also needs to mount the PVC from the previous step.
3. In every namespace that needs it, create a new PVC with the new provisioner. The namespace users don't need to know or care about the details of where the original mount lives, the NFS provisioner forwards those when needed.

Should I revive PR 1318?

[kmova]

Hi @therc, please go ahead with reviving the PR.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[zippyopstraining]

Hi Mr. Therc, actually let me explain my issue. I have my application which is running in NS1. That NS1 application has pv,pvc .Now i want to use the data of NS1 application in application of NS2 with new pv, pvc (like clone the NS1's pv). Is there any way?. You said that we can do "kubernetes-retired/external-storage#1210 (comment)" .There you mentioned ,we have to change "allow NFS_SERVER to be set to "auto" (or a new AUTO_NFS_SERVER=true)
allow NFS_PATH to be set to "clone" (or a new CLONE_NFS_PATH=true)" . where do i change this?

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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.