BGD-6242 Workspace stuck in starting due to missing volume

[HafdisE]

Jira ticket

https://spotinst.atlassian.net/browse/BGD-6242

Description

Add values config option to be able to specify the storage class of the PVC in the bigdata-notebook-workspace chart.

Demo

Given a values.yaml containing

pvc:
  storageClassName: pvc-ebs

A PVC with the following spec is generated:

spec:
  storageClassName: pvc-ebs
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi

Without providing a values.yaml:

spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi

Checklist

• I have added a Jira ticket link
• I have filled in the test plan
• I have executed the tests and filled in the test results
• I have updated/created relevant documentation

How to test

Helm install the chart with a valid value for pvc.storageClassName and check that it is successful and the PVC gets created with spec.storageClassName set to the provided value.

Test plan and results

Test	Description	Result	Notes
1	Manual helm install with storage class name set	✅	PV successfully created using storageClassName requested by PVC
2	Manual helm install without storage class name set	✅	PVC no longer specifies a storage class