External-storage: EFS-Provisioner option to not create subdir for each volume

Created on 19 Jun 2018 · 11Comments · Source: kubernetes-retired/external-storage

My goal is to create a statefulset where each member of the set has access to a single shared ReadOnlyMany volume, that gets prepopulated by a deployment before using.

I have turned to NFS, as aws ebs does not support ReadOnlyMany. However, using the efs-provisioner provisions a new directory in the nfs for each member of the set. However, I would like it to simply mount the nfs as a volume without creating a new subdirectory.

Is this possible, or am I barking up the wrong tree?

(my initial attempt to was to have a persistentvolumeclaim that just mounts an nfs pv, but i couldn't mount that more than once at a time for some reason)

lifecyclrotten

Source

ianseyer

Most helpful comment

That is a valid request.
Currently EFS provider creates folder for each PVC by unique name, with no option to change that.
I'd like to mount multiple PVCs in different Namespaces/Clusters under same EFS and share folder.

midN on 5 Mar 2019

👍2

All 11 comments

If you use a PVC in the StatefulSet outside of the PVC template, then all StatefulSet instances will share the same volume. Your initial attempt should have worked, so it may be worth further triaging that.

msau42 on 19 Jun 2018

👍1

midN on 5 Mar 2019

👍2

https://github.com/kubernetes-incubator/external-storage/pull/1147

midN on 11 Mar 2019

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-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 9 Jun 2019

Another perfect example of Issue being open for 1 year and being ignored with a valid PR addressing the issue, <3 Google

midN on 10 Jun 2019

👀1

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-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 10 Jul 2019

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-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 9 Aug 2019

@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-testing, kubernetes/test-infra and/or fejta.
/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.