fix: correct team names, and allowed orgs

2i2c-org / infrastructure

Infrastructure for configuring and deploying our community JupyterHubs.

https://infrastructure.2i2c.org

BSD 3-Clause "New" or "Revised" License

106 stars 65 forks source link

fix: correct team names, and allowed orgs #5108

Closed wildintellect closed 4 days ago

wildintellect commented 1 week ago

Org:teams need to be in allowed orgs before gpu access is allowed
Incorrect team was in the gpu section, the gpu team isn't listed in allowed orgs because a user needs to belong to one of the other allowed teams. Does this work @yuvipanda ?

github-actions[bot] commented 1 week ago

Merging this PR will trigger the following deployment actions.

Support and Staging deployments

Cloud Provider	Cluster Name	Upgrade Support?	Reason for Support Redeploy	Upgrade Staging?	Reason for Staging Redeploy
aws	nasa-veda	No		Yes	Following helm chart values files were modified: common.values.yaml

Production deployments

Cloud Provider	Cluster Name	Hub Name	Reason for Redeploy
aws	nasa-veda	prod	Following helm chart values files were modified: common.values.yaml

consideRatio commented 4 days ago

I think this should be fine and your understanding is correct; the typical issue here is allowing access to a profile choice but not allowing a login in the first place

github-actions[bot] commented 4 days ago

:tada::tada::tada::tada:

Monitor the deployment of the hubs here :point_right: https://github.com/2i2c-org/infrastructure/actions/runs/11888232121