jmte: create hub-specific nodegroups #5105
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
sgibson91
commented
Nov 14, 2024
sgibson91
commented
- fixes: AWS cost attribution: put each hub in jupyter-meets-the-earth into its own user nodegroup #5101
- sub-task of AWS cost attribution: split each hub in all of AWS clusters into their own user nodegroups #5074
|
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
sgibson91
commented
Nov 14, 2024
sgibson91
force-pushed
the
jmte/dedicated-nodegroups
branch
from
3662fa1
to
46cce04
Compare
|
So I went back and added node-purpose tags, and suddenly no more errors 🤷🏻♀️ |
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/11858488863 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.