Automate setup of dask-gateway jupyterhub service

[jhamman]

Automate setup of dask-gateway jupyterhub service

[tjcrone]

Is there a reason why we cannot just hard code it in each deployments configuration? I have done this for OOI, and it seems to be working. Still not able to access the dashboard but I just got it started.

[jhamman]

No reason except that it should be easily automated. For now, everyone should be overwriting this url value with their own deployment.

[tjcrone]

Yeah seems like it would be possible but I don't know what helm uses as the deployment variable off the top of my head.

On a related note, I have not seen any way to use a predefined static IP address for the two dask-gateway LoadBalancers, like we do for the proxy-public LoadBalancer. Have you seen where that configuration would live if it exists?

[jcrist]

On a related note, I have not seen any way to use a predefined static IP address for the two dask-gateway LoadBalancers, like we do for the proxy-public LoadBalancer. Have you seen where that configuration would live if it exists?

You'd set dask-gateway.schedulerProxy.service.loadBalancerIP and dask-gateway.webProxy.service.loadBalancerIP. See https://gateway.dask.org/install-kube.html#helm-chart-reference for the dask-gateway chart docs.

[jcrist]

How can we automatically determine this URL. Any Helm/k8s magic that can make this possible?

On initial investigation, it looks like helm doesn't allow templating values for subcharts (there's a few issues/stackoverflows about this, see e.g. https://stackoverflow.com/questions/55425688/helm-programmatically-override-subchart-values-yaml). My understanding is that if we wanted this behavior we'd need to use another tool to generate the values.yaml file for us. Yaml generating yaml generating yaml... I'm not sure what the best option is here.

[tjcrone]

This appears to be working for me: ooicloud/pangeo-cloud-federation@432ec42. I will do some more testing and then PR this.

[tjcrone]

Nope my bad. That did not appear to work. @jcrist was correct. 😁

Since we have so few deployments and it is just one line, seems like it would be okay to just plug this line into everyone's common.yaml file.

@jcrist thank you for the tips on defining the IP address!

[TomAugspurger]

This is done properly in dask/daskhub.