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

String replace ACMEv1 endpoints with v2 in docs

Browse Source
This commit is contained in:
James Munnelly 2018-04-12 19:07:53 +01:00
parent 9cebaa604f
commit d5c89aec28
6 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/issuers.rst
View File

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

2
docs/reference/issuers/acme/dns01.rst
View File

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

2
docs/reference/issuers/acme/http01.rst
View File

@ -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: {}

4
docs/tutorials/acme/dns-validation.rst
View File

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

4
docs/tutorials/acme/http-validation.rst
View File

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

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

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