Kernelspecs pvc has hardcoded name for volume as pvc-kernelspecs

[fresende]

Description

Kernelspecs pvc has hardcoded name for volume as pvc-kernelspecs

• enterprise_gateway/etc/kubernetes/helm/enterprise-gateway/templates/deployment.yaml

  Line 114 in ffebbaf

  volumeMounts:

• enterprise_gateway/etc/kubernetes/helm/enterprise-gateway/templates/deployment.yaml

  Line 118 in ffebbaf

  - name: pvc-kernelspecs

[kevin-bates]

Hi @fresende - thank you for opening this issue, and I sincerely apologize for the lack of a response.

Could you describe the issue with having a fixed PVC name? Are you trying to support multiple EG instances in the same Kubernetes cluster? What would you propose as a solution? I'm assuming you'd like to see a .Values item included so that the name could be set via a values.yaml file - is that the case?

Should we do the same for the nfs-kernelspecs and image-kernelspecs entries as well?

Thank you.