diff --git a/docs/tutorials/acme/dns-validation.rst b/docs/tutorials/acme/dns-validation.rst index 8e926e69b..f641559b7 100644 --- a/docs/tutorials/acme/dns-validation.rst +++ b/docs/tutorials/acme/dns-validation.rst @@ -148,18 +148,14 @@ successfully using ``kubectl describe``: $ kubectl describe certificate example-com Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Warning ErrorCheckCertificate 33s cert-manager-controller Error checking existing TLS certificate: secret "example-com-tls" not found - Normal PrepareCertificate 33s cert-manager-controller Preparing certificate with issuer - Normal PresentChallenge 33s cert-manager-controller Presenting dns-01 challenge for domain example.com - Normal PresentChallenge 33s cert-manager-controller Presenting dns-01 challenge for domain www.example.com - Normal SelfCheck 32s cert-manager-controller Performing self-check for domain example.com - Normal SelfCheck 32s cert-manager-controller Performing self-check for domain www.example.com - Normal ObtainAuthorization 6s cert-manager-controller Obtained authorization for domain example.com - Normal ObtainAuthorization 6s cert-manager-controller Obtained authorization for domain www.example.com - Normal IssueCertificate 6s cert-manager-controller Issuing certificate... - Normal CertificateIssued 5s cert-manager-controller Certificate issued successfully + Type Reason Age From Message + ---- ------ ---- ---- ------- + Normal CreateOrder 57m cert-manager Created new ACME order, attempting validation... + Normal DomainVerified 55m cert-manager Domain "example.com" verified with "dns-01" validation + Normal DomainVerified 55m cert-manager Domain "www.example.com" verified with "dns-01" validation + Normal IssueCert 55m cert-manager Issuing certificate... + Normal CertObtained 55m cert-manager Obtained certificate from ACME server + Normal CertIssued 55m cert-manager Certificate issued successfully You can also check whether issuance was successful with ``kubectl get secret example-com-tls -o yaml``. diff --git a/docs/tutorials/acme/http-validation.rst b/docs/tutorials/acme/http-validation.rst index 02d48f93f..e026ec1c1 100644 --- a/docs/tutorials/acme/http-validation.rst +++ b/docs/tutorials/acme/http-validation.rst @@ -147,18 +147,14 @@ successfully using ``kubectl describe``: $ kubectl describe certificate example-com Events: - Type Reason Age From Message - ---- ------ ---- ---- ------- - Warning ErrorCheckCertificate 33s cert-manager-controller Error checking existing TLS certificate: secret "example-com-tls" not found - Normal PrepareCertificate 33s cert-manager-controller Preparing certificate with issuer - Normal PresentChallenge 33s cert-manager-controller Presenting http-01 challenge for domain example.com - Normal PresentChallenge 33s cert-manager-controller Presenting http-01 challenge for domain www.example.com - Normal SelfCheck 32s cert-manager-controller Performing self-check for domain example.com - Normal SelfCheck 32s cert-manager-controller Performing self-check for domain www.example.com - Normal ObtainAuthorization 6s cert-manager-controller Obtained authorization for domain example.com - Normal ObtainAuthorization 6s cert-manager-controller Obtained authorization for domain www.example.com - Normal IssueCertificate 6s cert-manager-controller Issuing certificate... - Normal CertificateIssued 5s cert-manager-controller Certificate issued successfully + Type Reason Age From Message + ---- ------ ---- ---- ------- + Normal CreateOrder 57m cert-manager Created new ACME order, attempting validation... + Normal DomainVerified 55m cert-manager Domain "example.com" verified with "http-01" validation + Normal DomainVerified 55m cert-manager Domain "www.example.com" verified with "http-01" validation + Normal IssueCert 55m cert-manager Issuing certificate... + Normal CertObtained 55m cert-manager Obtained certificate from ACME server + Normal CertIssued 55m cert-manager Certificate issued successfully You can also check whether issuance was successful with ``kubectl get secret example-com-tls -o yaml``. diff --git a/docs/tutorials/acme/migrating-from-kube-lego.rst b/docs/tutorials/acme/migrating-from-kube-lego.rst index 87f54f5e2..cab2c2767 100644 --- a/docs/tutorials/acme/migrating-from-kube-lego.rst +++ b/docs/tutorials/acme/migrating-from-kube-lego.rst @@ -197,9 +197,9 @@ You should be able to verify the ACME account has been verified successfully: Server: https://acme-staging-v02.api.letsencrypt.org/directory Status: Acme: - Uri: https://acme-staging-v02.api.letsencrypt.org/acme/reg/5160358 + Uri: https://acme-staging-v02.api.letsencrypt.org/acme/acct/11217539 Conditions: - Last Transition Time: 2017-11-30T22:33:41Z + Last Transition Time: 2018-04-12T17:32:30Z Message: The ACME account was registered with the ACME server Reason: ACMEAccountRegistered Status: True