Jupyter Enterprise Gateway to also create an Ingress resource along with service for each driver pod to access Spark UI

[VisionMaverick]

Problem

• I want Jupyter Enterprise Gateway to also create an Ingress resource along with service for each driver pod to access Spark UI from the jupyter lab notebook
• This should be associated with each kernel pod

Proposed Solution

• Add Ingress Configuration: Modify the configurations or templates for Jupyter Enterprise Gateway to include specifications for an Ingress resource.

Additional context

• We have Jupyterhub + Jupyterlab single user server running in Kubernetes cluster. We are using Jupyter enterprise gateway to start spark kernel in Kubernetes cluster. As per current functionality Jupyter Enterprise gateway creates driver pod and Kubernetes service attached to the driver pod, but it does not provide functionality to create Ingress resource for the same. Because of this limitation we are not able to access Spark UI .

[welcome[bot]]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively. You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:

[lresende]

What kernelproxy are you using? If you use CRD with SparkOperator it has the ability to handle that for you automatically as part of the crd

[VisionMaverick]

Hi Luciano, Thanks a lot for the details. We are using KubernetesProcessProxy. Custom logic is associated with this, and moving to SparkOperatorProcessProxy is not an option.