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.

Sign up for GitHub

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

Jump to bottom

kitware: upgrade to k8s v1.30 and add hub-specific nodegroups #5128

Merged
merged 5 commits into from
Nov 18, 2024
Merged

kitware: upgrade to k8s v1.30 and add hub-specific nodegroups #5128

merged 5 commits into from
Nov 18, 2024

Conversation

sgibson91
Copy link
Member

@sgibson91 sgibson91 commented Nov 18, 2024 •
edited
Loading

@sgibson91 sgibson91 mentioned this pull request Nov 18, 2024
Closed
10 tasks
@github-actions GitHub Actions
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
aws kitware No Yes Following helm chart values files were modified: staging.values.yaml

Production deployments

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

@sgibson91 sgibson91 merged commit f777b56 into 2i2c-org:main Nov 18, 2024
8 checks passed
@sgibson91 sgibson91 deleted the kitware/dedicated-nodegroups branch November 18, 2024 11:07
@github-actions GitHub Actions
Copy link

🎉🎉🎉🎉

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AWS cost attribution: put each hub in kitware into its own user nodegroup
1 participant
@sgibson91