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
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?
The text was updated successfully, but these errors were encountered:
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:
projects
? something else?The text was updated successfully, but these errors were encountered: