Tweak memory guarantees for CarbonPlan's Azure hubs #878
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 will allow pods to be scheduled onto the nodes
|
This has already been deployed to the staging cluster and the four smallest nodes work fine. The two biggest nodes are not scaling due to a quota issue, but this uncovered the fact that the cluster is in the wrong location 🤦🏻♀️ #800 (comment) Therefore I'm going to merge this without review and work on migrating the cluster to the correct location |
|
Deployment to prod was successful |
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.
In #800 (comment), it was reported that scale-ups of the larger nodepools weren't happening due to insufficient memory issues. This PR fixes that issue for the
medium,largeandhugenodepools by reducing the memory guarantee.The
vhugeandvvhugenodepools are still causing issues. See #800 (comment) for details.