weiguoqiang/cert-manager
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #1017 from floyd-may/patch-1

Browse Source 
Update kube-lego migration guide towards logs
This commit is contained in:
jetstack-bot 2018-10-26 15:09:34 +01:00 committed by GitHub
commit a662b0eb3f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/tutorials/acme/migrating-from-kube-lego.rst
View File

@ -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.