| JupyterHub Infrastructure |  |
|---|---|
| Docker Image Build |  |
| qhub Auto Update |  |
This guide is intended to show how to deploy and maintain a jupyterhub cluster along with its related components. Infastructure as code is used, via GitHub Actions and Terraform, such that this repository will always reflect the exact state of the cluster. Advantages of this infrastructure as code approach:
- reduce the requirements for developers on their machines
- restrict modifications to infrastructure
- enable review of infastructure changes
- allow arbitrary users to request infrastructure changes
In practice GitHub Actions controls everything.
- awscli
- aws-iam-authenticator
- kubectl
- helm version 3+
- terraform version v0.13.4
Adding terraform-state and infastructure