helm: set default cpu/memory configuration for each ragflow component#21
Merged
Conversation
Signed-off-by: Mathieu Grzybek <mathieu@stackhpc.com>
Alex-Welsh
approved these changes
Jun 2, 2026
Member
Alex-Welsh
left a comment
Alex-Welsh
left a comment
There was a problem hiding this comment.
LGTM. Probably worth contributing these changes to the upstream repo as well https://github.com/infiniflow/ragflow
Author
|
I need to start from a clean branch to contribute upstream. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What problem does this PR solve?
The default deployment does not set
requests/limitsresources attributes to each pod. As a consequence, noisy neighbor and OOM effects can happen.This PR sets default resources to make sure that the scheduler can avoid overloading a node.
Type of change