-
Feature Request
-
Resolution: Done
-
Major
-
3.7.0.GA
-
False
-
None
-
False
-
Release Notes
-
-
Bug Fix
-
Done
-
-
Devfile schema allows to specify volume size
https://devfile.io/docs/2.2.0/adding-a-volume-component
When we create workspace with similar devfile, the volume size is always ignored and the custom size attribute is ignored.
To reproduce the issue:
- Use per-workspace persistent strategy in CheCluster CR
- Create workspace out of devfile which specifies volume size, i.e. https://github.com/agiertli/dev-spaces-test/blob/main/devfile.yaml#L29
schemaVersion: 2.1.0 metadata: name: sample-java-devfile components: - name: tools container: image: registry.redhat.io/devspaces/udi-rhel8:3.7 memoryLimit: 3Gi env: - name: USE_JAVA17 value: "true" endpoints: - exposure: public name: http-booster protocol: http targetPort: 8080 attributes: discoverable: true urlRewriteSupported: true - exposure: internal name: debug protocol: http targetPort: 5005 volumeMounts: - name: m2 path: /home/user/.m2 - name: m2 volume: size: 10G
- Confirm the PV/PVC size in the cluster - it should match in size, but it does not right now.
ACTUAL BEHAVIOUR:
volume size as defined in the devfile is ignored
EXPECTED BEHAVIOUR:
Volume size as defined in the devfile is respected by the dev spaces
