Skip to content
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

Don't give temple its own nodepool #3538

Merged
merged 2 commits into from
Dec 20, 2023
Merged

Conversation

yuvipanda
Copy link
Member

They never have had more than 20 users on at the same time in a while, and the huge dedicated node is costing them a lot more than needed.

They never have had more than 20 users on at the same time
in a while, and the huge dedicated node is costing them a lot
more than needed.
@yuvipanda yuvipanda requested a review from a team as a code owner December 19, 2023 03:08
Copy link

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
gcp 2i2c No Yes Following prod hubs require redeploy: temple

Production deployments

Cloud Provider Cluster Name Hub Name Reason for Redeploy
gcp 2i2c temple Following helm chart values files were modified: temple.values.yaml

@yuvipanda yuvipanda merged commit 045d2f2 into 2i2c-org:master Dec 20, 2023
9 checks passed
Copy link

🎉🎉🎉🎉

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done 🎉
Development

Successfully merging this pull request may close these issues.

1 participant