Specify resources for acme pods per issuer #6902
Open
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.
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