-
Notifications
You must be signed in to change notification settings - Fork 93
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
Removing custom dask_gateway from qhub and idle_timeout for dask clusters to 30 min #1151
Conversation
So, just to be sure. We will not support custom dask-gateway images then? |
@viniciusdc correct. The only reason that we used a custom version was due to needing a tls option to be set. |
@costrouc when you have some time, could you check the conflicts here? We tested this already right? |
Yeah @viniciusdc I will rebase and re-run the tests. |
Ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I tested it with a local deployment and with GCP. I was able to notice that the idle_timeout worked and killed the gateway cluster. No other issues with TLS as well, used lets-encrypt to test
Thanks for testing this @viniciusdc. Yes this will not fix the auth issues with jupyterlab extensions. |
This PR removed our custom dask-gateway image from the configuration.