Increasing limit because of prometheus container memory demand. #6227
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
|
|
|
🥰 Documentation preview ready! 🥰 Built with commit a71e5ea https://deploy-preview-6227--kyma-project-docs-preview.netlify.com |
|
@dekiel do I get it right, that the need is only for some pipelines of ours? if so, I would say we should not increate limits for entire Kyma but rather template the value and enable for overriding in our pipelines only |
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.
Description
After deploying stackdriver collector and defining additional grafana charts, prometheus container was suffering OOMKiler. We need incraese max container limit in limitrange to 6Gi as prometheus presented demand for at least 5Gi.
Changes proposed in this pull request:
Increasing max memory in kyma-default limitrange to 6Gi.
Related issue(s)
See also test infra issue #1623