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.

Sign up for GitHub

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

Jump to bottom

Persistent Volume strategies: add “per workspace” #21185

Closed
Tracked by #21254
, #21318
...
l0rd opened this issue Feb 20, 2022 · 1 comment
Closed
Tracked by #21254
, #21318
...

Persistent Volume strategies: add “per workspace” #21185

l0rd opened this issue Feb 20, 2022 · 1 comment
Assignees
@AObuchow
Labels
area/devworkspace-operator area/install Issues related to installation, including offline/air gap and initial setup kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.

Comments

@l0rd
Copy link
Contributor

l0rd commented Feb 20, 2022 •
edited
Loading

Is your enhancement related to a problem? Please describe

The only possible PVC strategy is “common”. But that doesn’t allow users to run more than one workspace at a time

Describe the solution you'd like

We should support another PV strategy: per workspace. This strategy associates a new PV to every new workspace
@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. area/devworkspace-operator severity/P1 Has a major impact to usage or development of the system. area/install Issues related to installation, including offline/air gap and initial setup labels Feb 20, 2022
@l0rd l0rd mentioned this issue Feb 20, 2022
Closed
41 tasks
@amisevsk amisevsk mentioned this issue Mar 8, 2022
Closed
@l0rd l0rd mentioned this issue Mar 15, 2022
Closed
35 tasks
@l0rd l0rd mentioned this issue Mar 25, 2022
Merged
11 tasks
@ibuziuk ibuziuk mentioned this issue Apr 4, 2022
Closed
45 tasks
@ibuziuk
Copy link
Member

ibuziuk commented Apr 27, 2022

Closing
DWO issue has been closed - devfile/devworkspace-operator#792

@ibuziuk ibuziuk closed this as completed Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AObuchow AObuchow

Labels
area/devworkspace-operator area/install Issues related to installation, including offline/air gap and initial setup kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@l0rd @ibuziuk @AObuchow