The 2i2c hubs use a custom hub image that is defined in the helm-charts directory of the infrastructure repository.
This custom hub image is built on top of the jupyterhub/k8s-hub Docker image and configured based on the needs of 2i2c hubs. This allows adding and configuring other packages like the jupyterhub-configurator or using specific versions of the spawner and authenticator. More information about this custom image can be found in the Dockerfile itself.
The 2i2c custom hub image is lives at Quay.io.
Updating the hub image#
When this hub image needs to be updated, the steps to take are:
Update the Dockerfile with any changes wanted
Commit the changes
git add helm-charts/images/hub/Dockerfile git commit
The commit SHA with be used to generate the image tag.
Rebuild the Docker image and push it to the Quay.io registry
@2i2caddress should give you access to push to the Quay.io registry where the hub image lives, but make sure you are logged into quay.io container registry with the right credentials and these creds are configured to have access to https://quay.io/repository/2i2c/pilot-hub. Please contact someone at 2i2c for access if this is not the case.
docker login quay.io
Checkout the Getting Started with Quay.io docs for more info.
Make sure you have jupyterhub/chartpress installed.
pip install chartpress
This package is also listed under
dev-requirements.txt, so it should be present if you’ve installed the dev dependencies.
Run chartpress to build the image, push it to the registry and update the basehub helm chart to use the updated image tag
Commit the changes made by
helm-charts/basehub/values.yaml, but discard the changes made to
helm-charts/basehub/Chart.yamlas the last may cause problems with the
git add helm-charts/basehub/values.yaml git commit