From d5c89aec289d4cc9573bfb1b90748b84de2bffbb Mon Sep 17 00:00:00 2001 From: James Munnelly Date: Thu, 12 Apr 2018 19:07:53 +0100 Subject: [PATCH] String replace ACMEv1 endpoints with v2 in docs --- docs/reference/issuers.rst | 4 ++-- docs/reference/issuers/acme/dns01.rst | 2 +- docs/reference/issuers/acme/http01.rst | 2 +- docs/tutorials/acme/dns-validation.rst | 4 ++-- docs/tutorials/acme/http-validation.rst | 4 ++-- docs/tutorials/acme/migrating-from-kube-lego.rst | 8 ++++---- 6 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/reference/issuers.rst b/docs/reference/issuers.rst index d88488b05..4abdb0e85 100644 --- a/docs/reference/issuers.rst +++ b/docs/reference/issuers.rst @@ -21,7 +21,7 @@ An example of an Issuer type is ACME. A simple ACME issuer could be defined as: spec: acme: # The ACME server URL - server: https://acme-v01.api.letsencrypt.org/directory + server: https://acme-v02.api.letsencrypt.org/directory # Email address used for ACME registration email: user@example.com # Name of a secret used to store the ACME account private key @@ -78,7 +78,7 @@ those credentials to perform the ACME DNS01 challenge with route53. name: letsencrypt-prod spec: acme: - server: https://acme-v01.api.letsencrypt.org/directory + server: https://acme-v02.api.letsencrypt.org/directory email: user@example.com privateKeySecretRef: name: letsencrypt-prod diff --git a/docs/reference/issuers/acme/dns01.rst b/docs/reference/issuers/acme/dns01.rst index 1c1a8c52d..af7b043ea 100644 --- a/docs/reference/issuers/acme/dns01.rst +++ b/docs/reference/issuers/acme/dns01.rst @@ -17,7 +17,7 @@ requests: spec: acme: email: user@example.com - server: https://acme-staging.api.letsencrypt.org/directory + server: https://acme-staging-v02.api.letsencrypt.org/directory privateKeySecretRef: name: example-issuer-account-key dns01: diff --git a/docs/reference/issuers/acme/http01.rst b/docs/reference/issuers/acme/http01.rst index 045207e2a..7a761ac49 100644 --- a/docs/reference/issuers/acme/http01.rst +++ b/docs/reference/issuers/acme/http01.rst @@ -20,7 +20,7 @@ using Ingress resources spec: acme: email: user@example.com - server: https://acme-staging.api.letsencrypt.org/directory + server: https://acme-staging-v02.api.letsencrypt.org/directory privateKeySecretRef: name: example-issuer-account-key http01: {} diff --git a/docs/tutorials/acme/dns-validation.rst b/docs/tutorials/acme/dns-validation.rst index cca296843..8e926e69b 100644 --- a/docs/tutorials/acme/dns-validation.rst +++ b/docs/tutorials/acme/dns-validation.rst @@ -28,7 +28,7 @@ You can read more about the Issuer resource in the :doc:`Issuer reference docs < namespace: default spec: acme: - server: https://acme-staging.api.letsencrypt.org/directory + server: https://acme-staging-v02.api.letsencrypt.org/directory email: user@example.com # Name of a secret used to store the ACME account private key @@ -65,7 +65,7 @@ production. Let's Encrypt's production environment imposes much stricter `rate limits`_, so to reduce the chance of you hitting those limits it is highly recommended to start by using the staging environment. To move to production, simply create a new Issuer with the URL set to -``https://acme-v01.api.letsencrypt.org/directory``. +``https://acme-v02.api.letsencrypt.org/directory``. The first stage of the ACME protocol is for the client to register with the ACME server. This phase includes generating an asymmetric key pair which is diff --git a/docs/tutorials/acme/http-validation.rst b/docs/tutorials/acme/http-validation.rst index b92312548..02d48f93f 100644 --- a/docs/tutorials/acme/http-validation.rst +++ b/docs/tutorials/acme/http-validation.rst @@ -30,7 +30,7 @@ You can read more about the Issuer resource in the :doc:`Issuer reference docs < spec: acme: # The ACME server URL - server: https://acme-staging.api.letsencrypt.org/directory + server: https://acme-staging-v02.api.letsencrypt.org/directory # Email address used for ACME registration email: user@example.com # Name of a secret used to store the ACME account private key @@ -46,7 +46,7 @@ production. Let's Encrypt's production environment imposes much stricter `rate limits`_, so to reduce the chance of you hitting those limits it is highly recommended to start by using the staging environment. To move to production, simply create a new Issuer with the URL set to -``https://acme-v01.api.letsencrypt.org/directory``. +``https://acme-v02.api.letsencrypt.org/directory``. The first stage of the ACME protocol is for the client to register with the ACME server. This phase includes generating an asymmetric key pair which is diff --git a/docs/tutorials/acme/migrating-from-kube-lego.rst b/docs/tutorials/acme/migrating-from-kube-lego.rst index 7562fc341..87f54f5e2 100644 --- a/docs/tutorials/acme/migrating-from-kube-lego.rst +++ b/docs/tutorials/acme/migrating-from-kube-lego.rst @@ -133,7 +133,7 @@ Your email address should be shown under the ``.data.lego.email`` field, and the ACME server URL under ``.data.lego.url``. For the purposes of this guide, we will assume the lego email is -``user@example.com`` and the URL ``https://acme-staging.api.letsencrypt.org/directory``. +``user@example.com`` and the URL ``https://acme-staging-v02.api.letsencrypt.org/directory``. Now that we have migrated our private key to the new Secret resource, as well as obtaining our ACME email address and URL, we can create a ClusterIssuer @@ -153,7 +153,7 @@ Create a file named ``cluster-issuer.yaml``: spec: acme: # The ACME server URL - server: https://acme-staging.api.letsencrypt.org/directory + server: https://acme-staging-v02.api.letsencrypt.org/directory # Email address used for ACME registration email: user@example.com # Name of a secret used to store the ACME account private key from step 3 @@ -194,10 +194,10 @@ You should be able to verify the ACME account has been verified successfully: Private Key Secret Ref: Key: Name: letsencrypt-private-key - Server: https://acme-staging.api.letsencrypt.org/directory + Server: https://acme-staging-v02.api.letsencrypt.org/directory Status: Acme: - Uri: https://acme-staging.api.letsencrypt.org/acme/reg/5160358 + Uri: https://acme-staging-v02.api.letsencrypt.org/acme/reg/5160358 Conditions: Last Transition Time: 2017-11-30T22:33:41Z Message: The ACME account was registered with the ACME server