extended operator resource memory limit #1231
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
HVBE
reviewed
Sep 6, 2023
There was a problem hiding this comment.
@imedaouidene Thanks for contributing! Makes sense to me
btw, out of interest, how big of a deployment, number of instances/dashboards/datasources wise are you running to hit this? This would be very valuable information for us!
Thanks!
HVBE
approved these changes
Sep 6, 2023
Thank you, Operator crashed when one Dashboard and one default instance of Grafana, it uses around 140 MiB for these two CRs . |
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.
OOM killed is encountered when running the operator on OpenShift environment.
extending memory limits to 256Mi