search

loft-sh / devpod-provider-kubernetes

DevPod on Kubernetes
Mozilla Public License 2.0
18 stars 15 forks source link

Whether it is necessary to need persistent volume or not to rely on storage #43

Open SilenceShine opened 5 months ago

SilenceShine commented 5 months ago

Whether it is necessary to need persistent volume or not to rely on storage

pascalbreuninger commented 5 months ago

@SilenceShine Thanks for opening the issue. Just to summarize, we'd need to remove the PVC and mount an emptyDir instead. This would require us to store metadata information on the pod instead of the PVC and essentially limit the lifetime of the workspace.

It's not the highest priority right now but if there's enough community interest we'll bump it up. Will leave this ticket open

LawiK974 commented 1 month ago

Hello, I have the need to offer to my developpers the ability to use devpod to test the build of their app directly in our k8s cluster but I don't need or want persistent volume for that. The build should always be done in a freshly bootstrap environment.

A way around this would be to provide an option to automatically delete the pvc after pod deletion, is it yet possible ? If not, should I open a new ticket for this ?

pascalbreuninger commented 1 month ago

Hey @LawiK974, DevPod automatically deletes the PVC if you delete the workspace. Is this enough for your use case?

doctorpangloss commented 1 month ago

for folks finding this issue, consider add the rancher local volume provisioner to your cluster to make things easier on yourself. devpod isn't the first or last application that expects to use persistent volume claims to provision storage.