Use request instead of limits for cpu resource #211
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
Since CPU is a compressible resource it makes sense for us not to limit it. Furthermore, since we want to meet the conditions for our node to be catalogued as `burstable` by Kubernetes we want to provide a `request` spec.
edif2008
approved these changes
Oct 9, 2024
edif2008
requested changes
Oct 9, 2024
edif2008
approved these changes
Oct 9, 2024
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.
Since CPU is a compressible resource it makes sense for us not to limit it. Furthermore, since we want to meet the conditions for our node to be catalogued as
burstableby Kubernetes we want to provide arequestspec.