Add/grafana/memory limits - #625
Merged
Merged
Conversation
Signed-off-by: Willi Carlsen <carlsenwilli@gmail.com>
Signed-off-by: Willi Carlsen <carlsenwilli@gmail.com>
SEQUOIIA
approved these changes
Jul 22, 2026
SEQUOIIA
left a comment
SEQUOIIA
left a comment
Member
There was a problem hiding this comment.
Surprised they wouldn't be using more memory, but speedier updateStrategy sounds good to me
Contributor
Author
They are reflecting production values. But you are right that some seem relatively low. |
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.
Fixes minor issues found related to Grafana workloads missing resources or rightsizing. Also found that rolloutstrategy was set wrong in the values.