This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
Bump Prometheus server resources #310
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
samvantran
approved these changes
Jun 24, 2020
branden
force-pushed
the
branden/prometheus-bump-resources
branch
from
2076532 to
5b9e77d
Compare
joejulian
approved these changes
Jun 24, 2020
joejulian
added a commit
that referenced
this pull request
Jul 8, 2020
* Bump prometheus resources * Add prometheus addon revision * Bump addon revision Co-authored-by: Joe Julian <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 type of PR is this?
Chore
What this PR does/ why we need it:
This bumps Prometheus server resources so that it is less likely to be throttled or OOM killed, while still keeping it small enough to be deployed on small clusters. This is in response to reports that Prometheus is running out of CPU and memory on small clusters (3 masters, 4-8 workers) without any workload besides the rest of KBA.
Which issue(s) this PR fixes:
https://jira.d2iq.com/browse/D2IQ-69451
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Checklist