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
Allow CA issuers to generate their own secrets #2479
Comments
Issues go stale after 90d of inactivity. |
Stale issues rot after 30d of inactivity. |
/kind feature In meantime you can use this as an alternative bu using the SelfSigned Issuer to create the CA cert for you:
|
@meyskens: The label(s) In response to this:
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. |
/remove-lifecycle rotten |
Issues go stale after 90d of inactivity. |
Stale issues rot after 30d of inactivity. |
Rotten issues close after 30d of inactivity. |
@jetstack-bot: Closing this issue. In response to this:
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. |
Is your feature request related to a problem? Please describe.
Currently, when creating a CA issuer, you have to manually generate a self signed cert for it (if that's what you want to use).
Describe the solution you'd like
Add an option to CA issuers to generate a self signed cert if its configured secret doesn't yet exist.
Additional context
If combined with #2478, CA issuers could be made to auto rotate their certificates when they are nearing expiration.
The text was updated successfully, but these errors were encountered: