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

nasa-ghg: put dask workers into their own nodepool per hub and tag them #5162

Merged
merged 3 commits into from
Nov 20, 2024
Merged

nasa-ghg: put dask workers into their own nodepool per hub and tag them #5162

merged 3 commits into from
Nov 20, 2024

Conversation

GeorgianaElena
Copy link
Member

Fixes #5155

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

Production deployments

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

@GeorgianaElena GeorgianaElena merged commit c07a4a0 into 2i2c-org:main Nov 20, 2024
8 checks passed
@GeorgianaElena GeorgianaElena deleted the dask-hub-split branch November 20, 2024 14:47
@github-actions GitHub Actions
Copy link

🎉🎉🎉🎉

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

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.

Split dask workers of each hub of nasa-ghg into their own nodegroup
1 participant
@GeorgianaElena