Skip to content

Allow cross DevWorkspace volumes #654

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

Closed
sleshchenko opened this issue Oct 21, 2021 · 1 comment
Closed

Allow cross DevWorkspace volumes #654

sleshchenko opened this issue Oct 21, 2021 · 1 comment

Comments

@sleshchenko
Copy link
Member

Description

It's supposed that there are several cases when using cross DevWorkspace volumes can be useful for optimization, like:

It may somehow be possible to archive with labeling PVC but I believe it supports only one volume mount path.

Unclear aspect:

  • user would needed to be aware of that fact and manually clean up cache to avoid exceeding PVC size;
  • at which level it should be defined? devfile? devworkspace? is it Che who reclaim user's volume to be cross namespace... Should be make all volumes cross deworkspaces be default and only scope projects? something else?
@sleshchenko
Copy link
Member Author

duplicates #630

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

1 participant