Customizable DNS Port

JupyterHub Zero to JupyterHub on Kubernetes
1

Hey there,

I am running JupyterHub on OpenShift, which requires some adjustments, but it works without modifying the JupyterHub Helm chart.

As pointed out by @Will_Holtam, OpenShift’s local DNS server runs on port 5353 instead of port 53.
The current workaround is to use kustomize to patch the ports.

The ports are specified in a named template.
I’m not that familiar with Helm but is it currently possible to set the ports via Helm values? And if not, do you think it should be made customizable since propably all OpenShift deployments have to patch the ports outside JupyterHub’s Helm chart?

Best regards
Paul

2

You shouldn’t need to patch the chart, you can add an additional *.networkPolicy.egress to allow the extra port:

What would be useful to know is if there’s anything required for OpenShift that can’t be configured using the existing values.yaml.

1 Like
3

You are absolutely right; it works without issues.

I’m already documenting my journey on deploying JupyterHub on an OpenShift cluster. I’m happy to share my findings once the deployment is completed, which should be in the next couple of weeks.

1 Like
4

That’d be great! Kubernetes on Red Hat OpenShift — Zero to JupyterHub with Kubernetes documentation links to GitHub - gembaadvantage/z2jh-openshift: A kustomization of the z2jh project so that it works with OpenShift. which has several kustomize patches, but it’s not clear to me whether all of those changes can also be made using the existing values.yaml parameters.