-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update to zero-to-jupyterhub 0.9.0 #20
Comments
testing this now on the new deployment,
however it is just easier to remove these 2 taints from the master node itself. |
good news, the fix of editing the label on the master node also fixes the volume attachment issue, so once I redeploy, I can re-enable persistent user storage. |
as part of #19, this is completed as well. |
Until now I have been using 0.8.2
0.9.0 was released 2 weeks ago, it upgrades to JupyterHub 1.1.0.
See changelog for 0.9.0: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/master/CHANGELOG.md#090---2020-04-15
The gitlab authentication #18 was not working with 0.8.2, it works fine with 0.9.0.
I authorized the whole SuperCDMS group to login, please let me know if there are issues.
the deployment is now at https://supercdms.jetstream-cloud.org/
@pibion
Persistent storage disabled
Warning, I currently had to disable persistent storage because there are some conflicts in the new release, I'll work to fix it in the next days and update this issue. This only affects the home of the Jupyter Notebook users, the data folder is not affected.
So you have some local storage, but if your session is killed, all your data is lost.
The text was updated successfully, but these errors were encountered: