[node-manager] added VPA for early-oom daemonset #2695
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
Signed-off-by: Denis Romanenko <denis.romanenko@flant.com>
RomanenkoDenys
added
the
area/cluster-and-infrastructure
|
🟢 Workflow details🟢 |
yalosev
approved these changes
Oct 10, 2022
apolovov
approved these changes
Oct 10, 2022
github-actions bot
pushed a commit
that referenced
this pull request
Oct 10, 2022
Signed-off-by: Denis Romanenko <denis.romanenko@flant.com>
|
Cherry pick PR 2703 to the branch release-1.37 successful! |
deckhouse-BOaTswain
added a commit
that referenced
this pull request
Oct 10, 2022
This was referenced Oct 10, 2022
Merged
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.
Signed-off-by: Denis Romanenko denis.romanenko@flant.com
Description
Added VPA for early-oom daemonset.
Why do we need it, and what problem does it solve?
Previously early-oom has static resources requests and limits(and requests = limits). On big nodes (>100 cpu) early-oom pod needs more cpu than allowed by limit. Standard solution - use VPA to calculate requests based on real cpu usage.
What is the expected result?
Checklist
Changelog entries