search

det-lab / jupyterhub-deploy-kubernetes-jetstream

CDMS JupyterHub deployment on XSEDE Jetstream
0 stars 1 forks source link

Update to zero-to-jupyterhub 0.9.0 #20

Closed zonca closed 4 years ago

zonca commented 4 years ago

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.

zonca commented 4 years ago

testing this now on the new deployment, the master now has 2 taints, so in order to be able to deploy proxy and hub into the master node we can add this tolerations to the proxy and hub pods:

  - effect: NoSchedule                                                                                                               
    key: CriticalAddonsOnly                                                                                                          
    operator: Equal                                                                                                                  
    value: "True"                                                                                                                    
  - effect: NoSchedule                                                                                                               
    key: dedicated                                                                                                                   
    operator: Equal                                                                                                                  
    value: master

however it is just easier to remove these 2 taints from the master node itself. Also because anyway we need it also for the singleuser containers.

zonca commented 4 years ago

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.

zonca commented 4 years ago

as part of #19, this is completed as well.