Repository navigation
Shared PVCs?
#2168
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
I just wanted to ask a question about recommended workflow for a particular usecase. I'd like to enable my developers to develop an application on a cluster, but one main usecase of this is that this application, in production, needs access to a large volume of read-only data to operate.
My prod helm chart creates a PVC for this volume and that works fine, as that PVC gets resolved to a PV, and that PV is then shared within the prod deployment's namespace among all the replicas. But in dev, obviously I'd like to be able to assign each developer their own namespace, to match devspace's assumptions, and two PVCs in different namespaces can't attach to the same PV.
I don't have an obvious solution to this. One bad solution is to resolve the separate PVs to the same underlying NFS filesystem (we're using EFS, and this is ... tricky ... on the efs csi provisioner, but I think possible), but this greatly complicates the helm chart and means it now has to know things it previously did not.
Are there best practices here that I haven't thought of?
Thanks!
All reactions