The JupyterHub team proudly announces the release of a helm chart for deploying JupyterHub on Kubernetes clusters. We've designed the JupyterHub helm chart to save you time in creating JupyterHub deployments.
You can find a repository with the helm chart here.
This is a pre-release version of the helm-chart. It will likely change in a breaking fashion sometime in the future, though we will make every effort to minimize this as much as possible as modifications are made for new features and increased stability. If you have any questions or comments, reach out to us on Gitter or open an issue. For help with deploying your own JupyterHub instance, see our guide for setting up JupyterHub (which uses this helm chart). Or, come find us at the JupyterHub talk at JupyterCon.
The following principles guided development:
Easy to administer
The nitty gritty of JupyterHub setup and management can be cumbersome, complicated, and time-consuming. With the JupyterHub helm chart, you will spend less time debugging your setup, and more time deploying, customizing to your needs, and successfully running your JupyterHub. Within a cloud computing infrastructure, using the helm chart typically requires only one or two commands to get started.
The JupyterHub helm chart uses applications and codebases that are open and thriving. We prefer, prioritize, and select tools that have a history of stability and development, and which adhere to open-source principles when it comes to project and community growth. As a result, you’ll be able to easily connect with the many tools available in the open-source community, and you’ll have flexibility in where you deploy JupyterHub.
We’ve made an effort to keep our helm chart as cloud-agnostic as possible. The only requirement is that your computing provider supports the Kubernetes infrastructure, an open-source platform that is widely available across many different online providers. You can run JupyterHub on cloud services such as Google Cloud, Microsoft Azure, and Amazon EC2, and even on your own hardware or institution-specific setup.
We've taken great care to develop the JupyterHub helm chart with the ability to be used in a variety of work, research, and education settings. Some JupyterHub deployments have a dynamic userbase that works in spurts of activity. Others have users that have long periods of inactivity. Rather than capping the amount of resources available for users, the JupyterHub helm chart utilizes Kubernetes to scale computational resources up (or down) as needed. This means that large changes in user behavior don’t result in system-wide instability or slowdown issues. It also means that you can quickly update user hardware, push new files to user disks, and alter the environment in which users are operating.
JupyterHub has been deployed in a variety of places, including at least one class with nearly 1500 students. We’ve made sure that it can handle large groups of users, and we’re excited to see people push the limit even further.
If you have any questions or comments, reach out to us on Gitter or open an issue. For help with deploying your own JupyterHub instance, see our guide, Zero to JupyterHub. Or, come find us at the JupyterHub talk at JupyterCon.
JupyterHub and this helm chart wouldn’t have been possible without the goodwill, time, and funding from a lot of different people. In particular, we want to thank the Gordon and Betty Moore Foundation, the Sloan Foundation, the Helmsley Charitable Trust, the Berkeley Data Science Education Program, and the Wikimedia Foundation for supporting various members of our team. We also want to thank the individuals of the JupyterHub team (listed below), the Project Jupyter community, and our more than 100 contributors for continuing to grow and improve this technology.
The JupyterHub Team (in alphabetical order)
Berkeley Data Science Education Program (Gunjan Baid, Sam Lau, Ryan Lovett, Yuvi Panda, Vinitra Swamy)
Cal Blueprint Team (Jiefu Gong, Sam Lau, Derrick Mar, Peter Veerman, Tony Yang)
Project Jupyter (Chris Holdgraf, Yuvi Panda, Min Ragan-Kelley, Carol Willing)