-
Notifications
You must be signed in to change notification settings - Fork 65
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
Provision per-cluster support components #456
Conversation
b08b645
to
f40f771
Compare
Multiple domains were supported primarily to make sure hubs are reachable by both datahub.mills.edu and mills.cloudbank.2i2c.cloud. In practice, nobody uses the second URL, and this just confuses the deployer code. datahub.mills.edu is a CNAME to mills.cloudbank.2i2c.cloud - but that doesn't require the latter to actually serve any content (over HTTP). CNAME is a DNS feature, so we don't actually have to do anything wrt HTTP serving. Includes slight refactoring to make auth.KeyProvider a little more agnostic to just using with JupyterHubs - could perhaps be used with 2i2c-org#456 in providing OAuth credentials for grafana too
- Follow-up to 2i2c-org#458 - domain can not be list anymore with 2i2c-org#460 - Support components config for each cluster is also now present in the cluster.yaml config files, with 2i2c-org#456. Even though that has not been merged yet, it is already deployed. This PR updates the schema to allow the support config.
Eventually this should be per-cluster auth via auth0, but this will do for now
Without this we were flying blind. Based off 2i2c-org#456
Without this we were flying blind. I manually updated the DNS records, and had to delete `proxy-public` svc to get this to work. Based off 2i2c-org#456
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great to me!
Copying testing instructions from #533 (comment):
|
For future readers, this is not the complete PR as it is described in the first message. Btw, @sgibson91, I think you will find that historical context useful as well 😉 . |
a dependent chart of our 'support' chart.
in a standard configuration.
avoid duplication
Ref #388
TODO