Deploying New Hubs

Creating a new hub

Each hub is configured by a “helm chart”. A chart is a set of configuration files written using YAML that describe the state we want the hub to be in. After you create a new chart describing a hub configuration and merge it, travis will take care of making the real world correspond to your wishes.

All the hub deployments are based on the Zero to JupyterHub guide (GitHub repository). The guide provides excellent advice on configuring your hub as well as a helm chart that we use. Each of the hubs here can use a different version of the Z2JH helm chart. This raises two questions: which version should I use and how do I find out what versions are available?

All versions of the JupyterHub helm charts are available from We are currently using a development release of the chart for most hubs. The reason for this is that a lot of new features have been added but no new release has been made (should happen in August 2018). If you do not know better picking the latest development release is a good choice.

To change the version of the hub that you are using edit hub-charts/<hubname>/requirements.yaml. The below snippet shows how to use v0.7-578b3a2:

- name: jupyterhub
  version: "v0.7-578b3a2"
  repository: ""

You can also inspect what version hub-charts/staginghub/requirements.yaml is using. Unless there are security related fixes or bugs that hinder your use of a specific version of a chart the recommendation is to not update your chart version during a workshop. Over the course of a semester it might be worth upgrading to the latest version, but should mostly be avoided.

Take a look at staginghub/ as an example chart to base yours on. A chart can describe anything from a simple to a very complex setup. We typically use them for low complexity things. The most important file is values.yaml which is where you configure your hub. Check the zero to JupyterHub guide for ideas on what you might want to configure.

Step one: Create a new hub directory

To begin your hub creation, first create a new directory in hub-charts/ with the name that you’d like your hub to have. The hub name should end with the word hub.

You need to edit jupyterhub.hub.baseUrl in your values.yaml and set it to the same name as the directory (we will use yourhubname-hub). The hub name will become a part of the hub URL, so pick a name wisely!


    baseUrl: /yourhubname-hub/

Step two: Setup authentication

Next decide how you’d like to authenticate your hub. You can use Github, Google or a “hash” based authenticator. Read more about Hub Authentication.

Step three: Update the travis build so it recognizes the new hub

Next, you need to update Travis (CI) instructions to test and automatically deploy the new hub. In the root directory of the hub-ops repo, look for the file: .travis.yml Add a new step to the script section AFTER all of the other listed hubs, but before the documentation step:

- |
  # Build <HUBNAME
  python ./ --no-setup --build <HUBNAME>

You also need to add your hub to the before_deploy section of the same file:

- |
  # Stage 3, Step XXX: Deploy the <HUBNAME>
  python ./ --build --push --deploy <HUBNAME>

Step four: Update the file with the hub name

Finally you need to list your <HUBNAME> as a valid chartname that recognises by editing permitted values of the chartname argument:

    help="Select which chart to deploy",
    choices=['staginghub', 'earthhub', 'wshub', 'monitoring', '<HUBNAME>']

Configuration values that need to remain secret can be stored in secrets/<hubname>.yaml.

Commit your changes to a new branch, make a PR, wait for the basic tests to run, check that travis looked at your new hub configuration, then merge the PR.

Once your hub is up and running you will be able to reach it at<hubname>.