Support externally-defined volume components #374
Labels
area/api
Enhancement or issue related to the api/devfile specification
area/devworkspace
Improvent or additions to the DevWorkspaces CRD
kind/enhancement
New feature or request
lifecycle/rotten
Rotten items. These items have been stale for 60 days and are now closed.
lifecycle/stale
Stale items. These items have not been updated for 90 days.
Is your feature request related to a problem? Please describe.
This issue is a follow-up to the second half of #310 -- supporting "external" volumes.
We've seen use cases where users have defined volumes on their cluster (configmaps/secrets or persistent storage) that they would like to use with their devfiles -- for example:
ROX
volume containing assets to workspacesImplementation options
There are various ways to go about this, all with drawbacks
externalVolume
?) to make the distinction between the two clearer and avoid ambiguity around other volume component fields.Additional context
The text was updated successfully, but these errors were encountered: