Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
SilenceShine opened this issue May 23, 2024 · 4 comments

Comments

@SilenceShine
Copy link

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

@pascalbreuninger
Copy link
Member

@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
Copy link

LawiK974 commented Sep 4, 2024

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
Copy link
Member

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

@doctorpangloss
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants