You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.
For security reasons, I think that the default configuration should not map the jupyter / scheduler services on a public IP address (even if jupyter notebook asks for a password, passing a password over HTTP without TLS is unsafe).
We could even have some dask-kubernetes helper commands to do that automatically and open the notebook and other HTTP status pages on http://localhost:localport instead.
The text was updated successfully, but these errors were encountered:
ogrisel
changed the title
Disable public access by default
Disable public IP access by default
Jan 18, 2018
A pretty common use case has been for sharing to share the scheduler or notebook - which would not work well with port forwarding/proxy.
(proxying is already used for the dashboard command)
It would be relatively easy to make the service creation optional and provide forward/proxy options - it would take a little effort, and complicate the CLI, perhaps.
Are you aware of the more recent and parallel daskernetes effort, and general chartification conversations?
For security reasons, I think that the default configuration should not map the jupyter / scheduler services on a public IP address (even if jupyter notebook asks for a password, passing a password over HTTP without TLS is unsafe).
It would be better to advertise the use of:
We could even have some
dask-kubernetes
helper commands to do that automatically and open the notebook and other HTTP status pages on http://localhost:localport instead.The text was updated successfully, but these errors were encountered: