jupyter-health: add experimental hub image with oauthenticator 17.1 #4968
Conversation
oauthenticator 17.1 adds PKCE, which the Jupyter Health deployment needs This experiment is no longer required once JupyterHub chart is updated to 4.0.0b4
|
Thank you @minrk! I'm working on getting this to land now |
consideRatio
force-pushed
the
oauth-17.1
branch
from
58003ad
to
12d6b52
Compare
|
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
| - name: support | ||
| images: | ||
| gcp-filestore-backups: | ||
| imageName: quay.io/2i2c/gcp-filestore-backups | ||
| valuesPath: gcpFilestoreBackups.image |
There was a problem hiding this comment.
Unrelated to this PR, but had to be cleaned up to get chartpress to build correctly so was done as part of this PR for simplicity - this image is now built in an external repo.
consideRatio
changed the title
|
Verified to startup correctly on staging, and the hub pod logs, and I've managed to login/logout/login without issues! |
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/11379935187 |
Thank you, I considered this but we lack a system to deploy two separate chart versions of z2jh currently in the CI/CD system so I figured we unblock this right away like this instead. Seeing oauthenticator 17.1 with PKCE verified to work without any issues against GitHub as an IDP was nice! |
|
This is now deployed! |
|
Thank you! |
oauthenticator 17.1 adds PKCE, which the Jupyter Health deployment is going to need quite shortly
This experiment is no longer required once JupyterHub chart is updated to >=4.0.0b4
I followed what I could of the steps for experimental images, but it looks like image registration on Quay.io and building with chartpress are not automated, so must be done by a person with 2i2c.org credentials.
btw, if it's possible to have a sample deployment migrated to the current beta of the chart, I'll volunteer Jupyter Health to be part of that, if that's easier than an experimental hub image. Jupyter Health will soon be using email addresses for login, which is a good exercise for the new kubespawner 7 slug scheme which handles email addresses differently.