docs: Document triggering a manual certificate renewal#443
Conversation
|
@marc1404: GitHub didn't allow me to request PR reviews from the following users: LucaBernstein. Note that only gardener members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn 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-sigs/prow repository. |
|
@LucaBernstein: changing LGTM is restricted to collaborators DetailsIn 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-sigs/prow repository. |
MartinWeindel
left a comment
There was a problem hiding this comment.
Thanks for adding the missing docu for manual renewal!
There is an additional complication if you want to perform manual renewal several times. Maybe it could be made obsolete with some additional implementation effort, but at the moment we should mention it.
Co-authored-by: Martin Weindel <martin.weindel@sap.com>
|
LGTM label has been added. DetailsGit tree hash: 198169239e852fc401fab5198753b864739b599e |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MartinWeindel The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
How to categorize this PR?
/kind enhancement
What this PR does / why we need it:
This PR documents how to trigger a manual
Certificaterenewal using the.spec.renewfield.Which issue(s) this PR fixes:
n.a.
Today, most readers would only learn about this mechanism through the
CertificateRevocationresource which also supports therenewfield. However, you don't need aCertificateRevocationto renew yourCertificateas you can achieve the same on the resource itself.Special notes for your reviewer:
/cc @MartinWeindel @LucaBernstein
Release note: