enterprise_gateway
enterprise_gateway copied to clipboard
Kernelspecs pvc has hardcoded name for volume as pvc-kernelspecs
Description
Kernelspecs pvc has hardcoded name for volume as pvc-kernelspecs
- https://github.com/jupyter-server/enterprise_gateway/blob/ffebbaff9184cc48e0c48c59682eac0a2fbf1c45/etc/kubernetes/helm/enterprise-gateway/templates/deployment.yaml#L114
- https://github.com/jupyter-server/enterprise_gateway/blob/ffebbaff9184cc48e0c48c59682eac0a2fbf1c45/etc/kubernetes/helm/enterprise-gateway/templates/deployment.yaml#L118
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.