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

Upstream a way to ensure our DaskClusters shut down if our user server does #87

Open
consideRatio opened this issue Oct 13, 2021 · 0 comments
Labels
🏷️ JupyterHub Something related to JupyterHub

Comments

@consideRatio
Copy link
Member

During the cryo meeting last week I said I thought that if a user server shut down, it would make us delete the user's created dask clusters using two separate mechanism, which the k8s native mechanism would be failsafe.

That was incorrect, but I want to explore if we can implement such feature. I opened dask/dask-gateway#451 regarding that and would be interested in trying to implement it if I conclude its viable and its found to be a wanted feature to add to the project. Some complexity will need to be added, so its absolutely a matter of considering if the complexity is worth it.

@consideRatio consideRatio added the 🏷️ JupyterHub Something related to JupyterHub label Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ JupyterHub Something related to JupyterHub
Projects
None yet
Development

No branches or pull requests

1 participant