Add instructions for accessing Dask Scheduler Dashboard from JupyterHub #953
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| jupyter-server-config: | ||
| mountPath: /etc/jupyter/jupyter_server_config.py | ||
| stringData: | | ||
| c.ServerProxy.host_allowlist = lambda app, host: True |
There was a problem hiding this comment.
We might want to note that this is inherently insecure.
…lambda app, host: True` for accessing Dask Scheduler Dashboard from Jupyter notebook
jacobtomlinson
approved these changes
Jun 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds documentation on how to enable access to Dask Scheduler Dashboards directly from Jupyter notebook instances spawned by JupyterHub. It covers configuring network policies, adding jupyter-server-proxy settings, and customizing Dask’s distributed.yaml, as mentioned in issue #952.