-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update memory limit of kube-state-metrics to 600Mi #12692
Update memory limit of kube-state-metrics to 600Mi #12692
Conversation
Hi @al-lac. Thanks for your PR. I'm waiting for a kubermatic member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@al-lac commit will need to be DCO signed, see this comment by our bot. |
Signed-off-by: al-lac <lackner.alex@gmail.com>
a8e9fc5
to
d3eae19
Compare
/ok-to-test |
/approve |
LGTM label has been added. Git tree hash: 07a06880a4a3ba863ad80ed63421563c16a9ec24
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
It increases the memory limit for the kube-state-metrics addon to
600Mi
Bigger clusters with a lot of namespaces and metrics have an increased memory usage for the kube-state-metrics pods which results in OOM kills. The increased limit makes it possible to use the addon on bigger clusters.
Which issue(s) this PR fixes:
Fixes #12689, kind of
What type of PR is this?
/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: