-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Azure deployment infrastructure #373
Comments
We have a lot of Azure automation at github.com/utoronto-2i2c/jupyterhub-deploy/. https://github.com/utoronto-2i2c/jupyterhub-deploy/tree/staging/terraform has terraform for setting up an AKS based Kubernetes cluster with autoscaling, image repositories and an NFS server in the correct network (via ansible), and there's automated deployment with hubploy and github actions. |
@yuvipanda thanks for that info! I've added a task to the top of the list to look into those repositories for inspiration |
Now that the JIL is up and running, is this mostly an issue for documentation rather than building the infrastructure itself? |
@choldgraf so #287 hasn't been merged (or marked for review) yet. I think once that's done this will be an issue of documentation |
@choldgraf #287 was indeed merged but the work @yuvipanda is talking about lives in #513 AFAIK, am I correct @yuvipanda? |
At this point, I think #512 and this issue completely overlap - so I'm going to close this one and develop that one. |
Summary
We currently focus much of our deployment infrastructure around Google Cloud rather than AWS or Azure. We also have a few clients that would like their hubs working on Azure. We should improve our Azure deployment infrastructure and use these use-cases as forcing functions.
The use-case we can use for this is:
The hub is currently running on Google Cloud, but they'd like us to move it to Azure whenever possible.
Acceptance criteria
We should be able to spin up an Pangeo-style hub on Azure with the same ease that we currently have with GKE.
Tasks to complete
The text was updated successfully, but these errors were encountered: