Specify resources for acme pods per issuer

[nabokihms]

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

Allow specifying resources requests/limits for acme solver pods per issuer

[jetstack-bot]

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[jetstack-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joshvanl for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cert-manager-prow]

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.