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 <fmay@asemio.com>
This commit is contained in:
parent
2f83424d4d
commit
f3bc8b5491
@ -246,16 +246,13 @@ There should be an entry for each ingress in your cluster with the kube-lego
|
|||||||
annotation.
|
annotation.
|
||||||
|
|
||||||
We can also verify that cert-manager has 'adopted' the old TLS certificates by
|
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
|
.. code-block:: shell
|
||||||
|
|
||||||
$ kubectl describe certificate my-example-certificate
|
$ kubectl logs -n kube-system -l app=cert-manager -c cert-manager
|
||||||
...
|
...
|
||||||
Events:
|
I1025 21:54:02.869269 1 sync.go:206] Certificate my-example-certificate scheduled for renewal in 292 hours
|
||||||
Type Reason Age From Message
|
|
||||||
---- ------ ---- ---- -------
|
|
||||||
Normal RenewalScheduled 1m cert-manager-controller Certificate scheduled for renewal in 292 hours
|
|
||||||
|
|
||||||
Here we can see cert-manager has verified the existing TLS certificate and
|
Here we can see cert-manager has verified the existing TLS certificate and
|
||||||
scheduled it to be renewed in 292h time.
|
scheduled it to be renewed in 292h time.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user