-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Allow HTTP01 solver pod to use non-default ServiceAccount #2770
Copy link
Copy link
Closed
Labels
area/apiIndicates a PR directly modifies the 'pkg/apis' directoryIndicates a PR directly modifies the 'pkg/apis' directorygood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Metadata
Metadata
Assignees
Labels
area/apiIndicates a PR directly modifies the 'pkg/apis' directoryIndicates a PR directly modifies the 'pkg/apis' directorygood first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Is your feature request related to a problem? Please describe.
We don't want to use the
defaultServiceAccount to run the solver-pod for HTTP01Describe the solution you'd like
We'd like to configure the ServiceAccount to use, preferably by allowing that to be specified within the
podTemplate-configuration in the solvers-stanza ( https://cert-manager.io/docs/configuration/acme/http01/#podtemplate )Describe alternatives you've considered
We've tried to find a way to configure this to no avail.
Additional context
Add any other context about the feature request here.
Environment details (if applicable):
/kind feature