basehub: allow shared-volume-reporter to be disabled, and disable it on 2i2c-aws-us and catalystproject-africa #4000
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
This comment was marked as resolved.
This comment was marked as resolved.
consideRatio
force-pushed
the
pr/optimize-2i2c-aws-us
branch
from
9d43587
to
e54dbeb
Compare
consideRatio
force-pushed
the
pr/optimize-2i2c-aws-us
branch
from
e54dbeb
to
e4fdd21
Compare
7 tasks
Specifically this cluster with its many hubs runs out of available pods per node on its core nodes, forcing two core nodes instead of one to be used. That in turn increase costs for the communities on this cluster with tens of percent. Without these pods that reports metrics only used for a graphana dashboard to conclude 100% of disk space is available on EFS without a storage limit - we could together with other optimizations become able to get down to using a single core node.
consideRatio
force-pushed
the
pr/optimize-2i2c-aws-us
branch
from
e4fdd21
to
75b1eb1
Compare
consideRatio
changed the title
|
I'll go for a self-merge here, it should be safe and can help me verify that we are indeed able to cut costs in 2i2c-aws-us and catalystproject-africa by reducing node pools form 2 to 1 nodes. |
|
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/8986256498 |
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.
Technically why this is acceptable is detailed in #3999.
2i2c-aws-us runs two core nodes, but only requires one for its CPU/memory needs. What makes us have two is the fact that we need room for 66 pods, but each core node only allows for 57 per node.
With this change, we reduce the pods to run on the core nodes with one pod per hub we have deployed --- 7 pods. And that in turn combined with other pod reductions like #3869 will get us below 57 pods to run on the core nodes, allowing us to cut cost for communities on 2i2c-aws-us (I think with almost 200USD total) and help us demonstrate more cost effective cloud operations.
Related