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
If component references non-declared volume - devworkspace should fail to start or failed to be created?
Probably failed to start since such validation needs external resources to be fetched like in plugins case. See below.
? mountSource: true should be converted to volume with name projects?
...
components:
- name: java-supportplugin:
id: redhat/java8/latestcomponents:
- name: vscode-java container:
memoryLimit: 2Gi
- name: m2# it already has volume define we just configure itvolume:
size: 2G
...
- name: maven-toolingcontainer:
image: registry.redhat.io/codeready-workspaces/stacks-java-rhel8:2.1mountSources: truememoryLimit: 768MivolumeMounts:
- name: m2# using volume from plugin definitionpath: /home/jboss/.m2
Which PVC strategy we should support in devworkspace? Probably common only - one PVC for one namespace. Should we implement the same isolation mechanism as for Che?
It's needed to implement Volume component that will define PVC or emptyDir with size configuration.
If component references non-declared volume - devworkspace should fail to start or failed to be created?
Probably failed to start since such validation needs external resources to be fetched like in plugins case. See below.
?
mountSource: true
should be converted to volume with name projects?Volume can be reused/configured from plugin. Like here https://github.com/devfile/api/blob/master/samples/devfiles/spring-boot-http-booster-devfile.yaml.
Which PVC strategy we should support in devworkspace? Probably common only - one PVC for one namespace. Should we implement the same isolation mechanism as for Che?
? Since plugins need volumes in initContainers, we can face issues with initSubpaths from initContainer
devworkspace-operator/pkg/controller/workspace/provision/deployment.go
Line 312 in 1b1bc9e
The text was updated successfully, but these errors were encountered: