-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Specify resources for acme pods per issuer #6902
base: master
Are you sure you want to change the base?
Specify resources for acme pods per issuer #6902
Conversation
This update introduces the ability to specify resource requests and limits for ACME Pods on a per-issuer basis. Now, users can define the resource requirements (CPU, memory, etc.) for each ACME Pod associated with a specific issuer, ensuring that the Pods adhere to the namespace's LimitRanges and are successfully created. This leads to more efficient resource usage and better compliance with namespace-level resource policies. Signed-off-by: m.nabokikh <maksim.nabokikh@flant.com>
Hi @nabokihms. Thanks for your PR. I'm waiting for a cert-manager 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
PR needs rebase. 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. |
Pull Request Motivation
This update introduces the ability to specify resource requests and limits for ACME Pods on a per-issuer basis. Now, users can define the resource requirements (CPU, memory, etc.) for each ACME Pod associated with a specific issuer.
This is required to ensure that the Pods adhere to the namespace's LimitRanges and are successfully created. This leads to more efficient resource usage and better compliance with namespace-level resource policies.
Kind
feature
Release Note