Fix 29GB RAM profile option not starting in openscapes #3791
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
Looks like the overhead of resources in AWS nodes has changed since we last set these, causing the largest pod on r5.xlarge to not fit anymore. We should eventually dynamically generate these - but in the meantime, I've just regenerated these numbers using our existing deployer command so mem_29_7 starts again.
|
Came up during discussion of #3743 |
|
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
sgibson91
approved these changes
Mar 12, 2024
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/8252554691 |
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.
Looks like the overhead of resources in AWS nodes has changed since we last set these, causing the largest pod on r5.xlarge to not fit anymore. We should eventually dynamically generate these
- but in the meantime, I've just regenerated these numbers using our existing deployer command so mem_29_7 starts again.