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

victor, jmte: fix some dask new nodegroups setup #5169

Merged
merged 3 commits into from
Nov 21, 2024
Merged

victor, jmte: fix some dask new nodegroups setup #5169

merged 3 commits into from
Nov 21, 2024

Conversation

GeorgianaElena
Copy link
Member

@GeorgianaElena GeorgianaElena commented Nov 21, 2024 •
edited
Loading

Fixes #5075

@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 victor No Yes Following helm chart values files were modified: staging.values.yaml

Production deployments

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

@GeorgianaElena GeorgianaElena merged commit 473d616 into 2i2c-org:main Nov 21, 2024
7 of 8 checks passed
@GeorgianaElena GeorgianaElena deleted the dask-hub-split branch November 21, 2024 11:00
@github-actions GitHub Actions
Copy link

🎉🎉🎉🎉

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

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: split dask workers of each hub in all clusters into their own nodegroups
1 participant
@GeorgianaElena