-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update workspace storage docs to mention DWO's storage strategy attribute #22316
Comments
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
/remove-lifecycle stale |
/remove-lifecycle stale |
Reopening for clarification, is it really completed cc: @deerskindoll @AObuchow |
not completed, I removed the |
@ibuziuk: @deerskindoll is correct, this has not been resolved. Though it's still debatable whether this is worth documenting:
|
Is your enhancement related to a problem? Please describe
The Che documentation on requesting persistent workspace storage currently mentions mounting volumes and PVCs.
However, there is no mention of DWO's ability to automatically provision storage by creating a PVC, which can be configured on a per-workspace basis with the
controller.devfile.io/storage-type
attribute.Describe the solution you'd like
The Che documentation should explain the usage of the
controller.devfile.io/storage-type
attribute.Describe alternatives you've considered
We may not want to document this attribute, as it is "internal" (part of DWO's API, not Che) and Che already configures this attribute from the user dashboard.
Furthermore, users are most likely going to configure persistent storage for their workspaces using the Dashboard UI and not by modifying their devfile or devworkspace.
Additional context
No response
The text was updated successfully, but these errors were encountered: