You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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!
Beta Was this translation helpful? Give feedback.
All reactions