Proxy for worker and scheduler dashboards about dask-kubernetes HOT 4 CLOSED

Sorry that nobody responded to this issue.

I imagine much of this has been superseded with the dask labextension. You can also access worker dashboards via the scheduler dashboard using the same techniques.

I'm going to close this as out of date, but if I've gotten the wrong end of the stick please don't hesitate to ask for it to be reopened.

from dask-kubernetes.

Is there a native way to tell the labextension to point at a scheduler that's behind a single HTTPS endpoint? I know there was talk of something that depends on a change to jupyter-server-proxy but I don't know if that ever got merged.

from dask-kubernetes.

I'm not sure if I understand the question. You can currently provide the extension with the URL of the dashboard, or it will attempt to autodetect it from the cluster object.

from dask-kubernetes.

Ohhhh...yeah, I need to try feeding the internal URL to the dashboard connection widget. The way I've been doing it, via jupyter-server-proxy works, but it's probably not necessary now that the lab extension exists. I had forgotten that I created the proxy (and the worker scheduler proxies) as a way to get a new browser tab open pointing at the dashboard initially.

from dask-kubernetes.