-
Notifications
You must be signed in to change notification settings - Fork 60
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
QCL add cluster yaml, config, staging hub #2295
Conversation
pnasrat
commented
Mar 2, 2023
- Add cluster file for QCL hub
- Generate QCL cluster config and support secrets
- See [QCL] Tracking: New Hub Deployment #2287
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.
Some notes about domain names
Getting API rate limited but local validate fails. Will fix up after lunch
|
Note to self validate runs
|
Sigh obvious typo now validate fails with
|
When using basehub, your values should not be indented under basehub. The daskhub chart dependa on basehub, so basehub chart config is nested under such key for a daskhub chart |
Tested TLS working correctly via
|
for more information, see https://pre-commit.ci
Typo Co-authored-by: Erik Sundell <erik.i.sundell@gmail.com>
Domain name fix Co-authored-by: Erik Sundell <erik.i.sundell@gmail.com>
Domain name fixes Co-authored-by: Erik Sundell <erik.i.sundell@gmail.com>
for more information, see https://pre-commit.ci
Based off practices in utoronto hub and that the hubs reference table only uses the 2i2c.cloud urls so should support both Note as we use grafana hub ingress rule that is handled differently to the support helm-chart redirect template for hub urls
for more information, see https://pre-commit.ci
Actually need to add enc-staging values file before review |
Deployed staging hub here https://staging.quantifiedcarbon.com/hub/login?next=%2Fhub%2F I may need to get the auth wired in |
for more information, see https://pre-commit.ci
Ready for review PTAL. Staging hub is up from a manual deploy. Then will do further configuration under main tracking issue. |
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.
Nice work this looks great!!
Things I figure remains in our out of this PR are:
- Redirects for prod / grafana
- Prod hub
- admin_users to include listed accounts from QCL
- singleuser.profileList configuration
grafana: | ||
grafana.ini: | ||
server: | ||
root_url: https://grafana.quantifiedcarbon.com/ | ||
auth.github: | ||
enabled: true | ||
allowed_organizations: 2i2c-org | ||
ingress: | ||
hosts: | ||
- grafana.qcl.2i2c.cloud | ||
- grafana.quantifiedcarbon.com | ||
tls: | ||
- secretName: grafana-tls | ||
hosts: | ||
- grafana.qcl.2i2c.cloud | ||
- grafana.quantifiedcarbon.com |
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.
I considered this config quite a bit, thinking that perhaps it was important to list grafana.quantifiedcarbon.com
as the topmost host. I think it may not be important based on investigation in #2304 though.
What do you think about going for grafana.quantifiedcarbon.com
as the first entry systematically in lists to reduce a risk of issues for now?
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.
I'll read through your investigation on #2304 and this can be updated if need be before we enable the prod hub and handover to the community
redirects: | ||
rules: | ||
- from: staging.qcl.2i2c.cloud | ||
to: staging.quantifiedcarbon.com |
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.
Nice work figuring this out! I wasn't aware of this system to create Ingress resources was available in the basehub
helm chart, and suspect it may not have been documented either yet.
We should have redirect rules for grafana and the production hub here as well. Maybe the production hub is out of scope for this PR and thats fine.
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.
There is some documentation here https://infrastructure.2i2c.org/en/latest/howto/manage-domains/index.html
I think when we start work on the deployer improvments making the generator take optional args for custom domains might help
Yes I think this is good to go and I'll split out the prod hub.
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/4343972840 |