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

investigate whether /kurtosis-data has to be persistent in non production enclaves #2021

Open
h4ck3rk3y opened this issue Jan 5, 2024 · 0 comments
Labels
bug Something isn't working painful Painful bug

Comments

@h4ck3rk3y
Copy link
Contributor

What's your CLI version?

0.85.55

Description & steps to reproduce

In December I used the Docker pattern wher ethe /kurtosis-data is always persistent and copied it over to Kubernetes. But some users are showing concerns around it always being persistent.

People need the right storage class configured
Enclave creation time goes up slightly
It consumes a persistent volume

Desired behavior

Figure out whether its actually needed an useful

What is the severity of this bug?

Painful; this is causing significant friction in my workflow.

What area of the product does this pertain to?

Other: anything not covered by the above

@h4ck3rk3y h4ck3rk3y added the bug Something isn't working label Jan 5, 2024
@github-actions github-actions bot added the painful Painful bug label Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working painful Painful bug
Projects
None yet
Development

No branches or pull requests

1 participant