Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permissions dask cluster #1

Open
zonca opened this issue Apr 25, 2018 · 1 comment
Open

Permissions dask cluster #1

zonca opened this issue Apr 25, 2018 · 1 comment
Assignees

Comments

@zonca
Copy link
Owner

zonca commented Apr 25, 2018

Now dask-kubernetes has support for RBAC, see pangeo-data/pangeo#172.

However a Jupyter single-user pod of a user still has enough permissions to kill another user Jupyter or dask pod.
The solution would be namespaces, but it requires a large amount of work, see:
https://github.com/pangeo-data/pangeo/issues/135#issuecomment-384320753

@rsignell-usgs I suggest for now to go ahead and assume it is not a big deal and users won't try to delete other resources, is it ok?

If so I'll go ahead and try a complete deployment of Jupyterhub + dask-kubernetes (with each user being able to spawn clusters) + test reading zarr files.

@zonca zonca self-assigned this Apr 25, 2018
@rsignell-usgs
Copy link

Yes, since pangeo hasn’t had problems yet, it seems reasonable. Also we will control users!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants