raise cert-manager resource limits to prevent OOMKills #6216
Conversation
kubermatic-bot
added
release-note
kubermatic-bot
added
the
size/S
|
/cherrypick release/v2.15 |
|
@xrstf: once the present PR merges, I will cherry-pick it on top of release/v2.15 in a new PR and assign it to you. In response to this:
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. |
|
[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 |
kubermatic-bot
added
the
approved
|
/lgtm |
|
LGTM label has been added. Git tree hash: a89f95105581259a6028c9bf4643b50bfd00c0cf
|
|
@xrstf: new pull request created: #6218 In response to this:
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. |
What this PR does / why we need it:
The 30MB limit for cert-manager is too restrictive, it began to crashloop even just managing 5 certificates in my cluster.
Does this PR introduce a user-facing change?: