From f3bc8b54913804293a8b06557ee8630acdbcc401 Mon Sep 17 00:00:00 2001 From: Floyd May Date: Fri, 26 Oct 2018 08:46:24 -0500 Subject: [PATCH] Update kube-lego migration guide towards logs Related to #773 - the previous instructions guide the user to look for events on the certificate related to when renewals are scheduled. This change directs them to view the logs to see the renewal schedule messages. Signed-off-by: Floyd May --- docs/tutorials/acme/migrating-from-kube-lego.rst | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/docs/tutorials/acme/migrating-from-kube-lego.rst b/docs/tutorials/acme/migrating-from-kube-lego.rst index dc377139c..7a17c8f76 100644 --- a/docs/tutorials/acme/migrating-from-kube-lego.rst +++ b/docs/tutorials/acme/migrating-from-kube-lego.rst @@ -246,16 +246,13 @@ There should be an entry for each ingress in your cluster with the kube-lego annotation. We can also verify that cert-manager has 'adopted' the old TLS certificates by -'describing' one of these newly created certificates: +viewing the logs for cert-manager: .. code-block:: shell - $ kubectl describe certificate my-example-certificate + $ kubectl logs -n kube-system -l app=cert-manager -c cert-manager ... - Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Normal RenewalScheduled 1m cert-manager-controller Certificate scheduled for renewal in 292 hours + I1025 21:54:02.869269 1 sync.go:206] Certificate my-example-certificate scheduled for renewal in 292 hours Here we can see cert-manager has verified the existing TLS certificate and scheduled it to be renewed in 292h time.