-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Be able to specify a serviceAccount for the HTTP01 ACME solver pod #3852
Copy link
Copy link
Closed
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Description
When deploying cert-manager using the Helm chart, we can specify the serviceAccount to use for:
- the Webohook
- the CA injector
- the deployment
But we can't specify it for the HTTP01 ACME solver pod.
The problems with this are:
- If the default serviceAccount is disabled, we need to provide a custom one
- We can't use a serviceAccount with linked imagePullSecrets to be able to pull the solver image from private registries in air gapped environments
- We can't apply PSPs to the solver pod.
To solve this, we propose to add a parameter --acme-http01-solver-service-account to cert-manager deployment to specify the serviceAccount to use in every namespace.
/kind feature
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.