JupyterHub on Kubernetes-- Helm Chart簡介

JupyterHub on Kubernetes-- Helm Chart簡介

目前，JupyterHub支持在Kubernetes上的Helm Chart安裝，（2018.06）最新版本是0.6。

• 本文來源，https://blog.jupyter.org/announcing-the-jupyterhub-helm-chart-v0-5-fa532bb8519d?gi=9c7d9c2fd2d5
• 本文地址，http://www.javashuo.com/article/p-npwqajxc-cg.html，by openthings，2018-06.28.
• 更多內容，參考 JupyterHub on Kubernetes部署與應用指南 。
• 參考資料：
  • 官方文檔，JupyterHub documentation
  • 開發源碼，JupyterHub development repository
  • Helm項目，JupyterHub Helm Chart development repository
  • 部署JupyterHub到Kubernetes，Zero to JupyterHub guide

JupyterHub 使得對多個用戶提供不一樣的Jupyter服務實例成爲可能（Jupyter自己已經能夠讓多個用戶使用同一個實例，並且共享裏面的數據和代碼）。經過 JupyterHub Helm Chart，能夠進一步安裝到 kubernetes 中去運行，從而使JupyterHub 具備更好的伸縮性、穩定性和靈活性，甚至於能夠在同一個集羣中運行多個隔離的JupyterHub環境，方便地進行數據探索和模型測試，快速進行環境遷移部署，支持運行資源的調配和狀態監控。

咱們JupyterHub團隊很是高興滴宣佈JupyterHub Helm Chart的新版本: version 0.5發佈（本文翻譯時已經是0.6）。這裏描述了該release的新特性.。We’ve nicknamed the releases of the JupyterHub Helm Chart after famous cricketers, in this case world-class bowler Hamid Hassan*.

該版本應用JupyterHub 0.8, 加入了更好的HTTPS 支持，改進了伸縮性到 ~4,000 同時用戶。查看 Helm Chart Changelog 得到更多信息。

新特性

添加到v0.5的新特性：

JupyterHub 0.8

 JupyterHub 0.8 包含了不少新特性，其中不少得益於JupyterHub到 Kubernetes的部署，下面是與 Helm Chart configuration 有關的說明：

1. Lots of performance improvements. We now know we can handle up to 4k active users.
2. Limit the number of users who can try to launch the hub at once. This can be tuned to avoid crashes when hundreds of users try to launch at the same time. It gives them a friendly error message and asks them to try later. See hub.concurrentSpawnLimit.
3. Limit the number of simultaneous active users . The Active Server limit can be used to limit the total number of active users that can use the hub at any given time. This allows admins to control the size of their clusters more effectively. See hub.activeServerLimit.
4. Memory limits & guarantees can now contain fractional units. So you can say 0.5G instead of having to use 512M.
5. No more ‘too many redirects’ errors at scale. This fixes an annoying race condition causing users to get stuck in a redirect loop when starting their servers.

Easier HTTPS

Version 0.5 of the helm chart makes it easier for admins to set up HTTPS for their users with Let’s Encrypt. Users often access a JupyterHub instance from a public URL. To avoid nefarious behavior and increase security, using HTTPS is important. You can now choose to use Let’s Encrypt or a valid HTTPS certificate and key. You can also use your own HTTPS certificates & keys rather than using Let’s Encrypt. You can find the new instructions here.

More authenticators

Authenticators allow you to control who has access to your JupyterHub. The following new authentication providers have been added in 0.5:

1. GitLab
2. CILogon
3. Globus

You can now also set up a whitelist of usernames that have access to the hub (in addition to other authenticators in use). Do so by adding to the list in auth.whitelist.users.

Hub Services support

Services let you connect your JupyerHub to other web services (for example, in mybinder.org). You can now add external JupyterHub Services by adding them to hub.services. Note that you are still responsible for actually running the service somewhere (perhaps as a deployment object in Kubernetes).

More customization with jupyterhub_config.py

Sometimes it is useful to be able to run arbitrary extra code when setting up your deployment. You can put extra snippets of jupyterhub_config.py configuration in hub.extraConfig. Now you can also add extra environment variables to the hub in hub.extraEnv and extra configmap items via hub.extraConfigMap. This makes it cleaner to customize the hub's configuration in ways that are not yet possible with config.yaml. You can find more information in the documentation.

More customization options for user server environments

More options have been added under singleuser to help you customize the environment that the user session is spawned in. You can…

• Change the uid / gid of the user with singleuser.uid and singleuser.fsGid
• Mount extra volumes with singleuser.storage.extraVolumes & singleuser.storage.extraVolumeMounts
• Provide extra environment variables with singleuser.extraEnv.

More information

*Hamid Hassan is a fast bowler who currently plays for the Afghanistan National Cricket Team. With nicknames ranging from 「Afghanistan’s David Beckham」 to 「Rambo」, he is considered by many to be Afghanistan’s first Cricket Superhero. Currently known for fast (145km/h+) deliveries, cartwheeling celebrations, war painted face and having had to flee Afghanistan as a child to escape from war. He says he plays because 「We are ambassadors for our country and we want to show the world that Afghanistan is not like people recognize it by terrorists and these things. We want them to know that we have a lot of talent as well.」