mirror of
https://github.com/wahyd4/cert-manager.git
synced 2026-08-09 05:06:38 +10:00
Update API group in docs
Signed-off-by: James Munnelly <james@munnelly.eu>
This commit is contained in:
James Munnelly
@@ -76,7 +76,7 @@ Deploy that version with helm
|
||||
# IMPORTANT: if you are deploying into a namespace that **already exists**,
|
||||
# you MUST ensure the namespace has an additional label on it in order for
|
||||
# the deployment to succeed
|
||||
$ kubectl label namespace <deployment-namespace> certmanager.k8s.io/disable-validation="true"
|
||||
$ kubectl label namespace <deployment-namespace> cert-manager.io/disable-validation="true"
|
||||
|
||||
# Install our freshly built cert-manager image
|
||||
$ helm install \
|
||||
|
||||
@@ -51,7 +51,7 @@ cert-manager runs in:
|
||||
.. code-block:: shell
|
||||
|
||||
# Disable resource validation on the cert-manager namespace
|
||||
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
|
||||
kubectl label namespace cert-manager cert-manager.io/disable-validation=true
|
||||
|
||||
You can read more about the webhook on the :doc:`webhook document <../webhook>`.
|
||||
|
||||
@@ -126,7 +126,7 @@ In order to install the Helm chart, you must run:
|
||||
kubectl create namespace cert-manager
|
||||
|
||||
# Label the cert-manager namespace to disable resource validation
|
||||
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
|
||||
kubectl label namespace cert-manager cert-manager.io/disable-validation=true
|
||||
|
||||
# Add the Jetstack Helm repository
|
||||
helm repo add jetstack https://charts.jetstack.io
|
||||
@@ -178,7 +178,7 @@ to issue basic certificate types:
|
||||
metadata:
|
||||
name: cert-manager-test
|
||||
---
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: test-selfsigned
|
||||
@@ -186,7 +186,7 @@ to issue basic certificate types:
|
||||
spec:
|
||||
selfSigned: {}
|
||||
---
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: selfsigned-cert
|
||||
|
||||
@@ -64,7 +64,7 @@ cert-manager runs in:
|
||||
.. code-block:: shell
|
||||
|
||||
# Disable resource validation on the cert-manager namespace
|
||||
oc label namespace cert-manager certmanager.k8s.io/disable-validation=true
|
||||
oc label namespace cert-manager cert-manager.io/disable-validation=true
|
||||
|
||||
You can read more about the webhook on the :doc:`webhook document <../webhook>`.
|
||||
|
||||
|
||||
@@ -32,17 +32,17 @@ label:
|
||||
kubectl describe namespace cert-manager
|
||||
|
||||
Name: cert-manager
|
||||
Labels: certmanager.k8s.io/disable-validation=true
|
||||
Labels: cert-manager.io/disable-validation=true
|
||||
Annotations: <none>
|
||||
Status: Active
|
||||
...
|
||||
|
||||
If you cannot see the ``certmanager.k8s.io/disable-validation=true`` label on
|
||||
If you cannot see the ``cert-manager.io/disable-validation=true`` label on
|
||||
your namespace, you should add it with:
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
|
||||
kubectl label namespace cert-manager cert-manager.io/disable-validation=true
|
||||
|
||||
Please continue reading this guide once you have added the label.
|
||||
|
||||
@@ -61,12 +61,12 @@ We can first check for the existence of the CustomResourceDefinition resources:
|
||||
|
||||
kubectl get crd | grep certmanager
|
||||
|
||||
NAME CREATED AT
|
||||
certificates.certmanager.k8s.io 2018-08-17T20:12:26Z
|
||||
challenges.certmanager.k8s.io 2018-08-02T15:33:02Z
|
||||
clusterissuers.certmanager.k8s.io 2018-08-17T20:12:26Z
|
||||
issuers.certmanager.k8s.io 2018-08-17T20:12:26Z
|
||||
orders.certmanager.k8s.io 2018-08-02T14:40:11Z
|
||||
NAME CREATED AT
|
||||
certificates.cert-manager.io 2018-08-17T20:12:26Z
|
||||
challenges.cert-manager.io 2018-08-02T15:33:02Z
|
||||
clusterissuers.cert-manager.io 2018-08-17T20:12:26Z
|
||||
issuers.cert-manager.io 2018-08-17T20:12:26Z
|
||||
orders.cert-manager.io 2018-08-02T14:40:11Z
|
||||
|
||||
We should then also check for that the webhook's Issuer and Certificate
|
||||
resources exist and have been issued correctly:
|
||||
@@ -75,13 +75,13 @@ resources exist and have been issued correctly:
|
||||
|
||||
kubectl get issuer,certificate --namespace cert-manager
|
||||
|
||||
NAME AGE
|
||||
issuer.certmanager.k8s.io/cert-manager-webhook-ca 22d
|
||||
issuer.certmanager.k8s.io/cert-manager-webhook-selfsign 22d
|
||||
NAME AGE
|
||||
issuer.cert-manager.io/cert-manager-webhook-ca 22d
|
||||
issuer.cert-manager.io/cert-manager-webhook-selfsign 22d
|
||||
|
||||
NAME READY SECRET AGE
|
||||
certificate.certmanager.k8s.io/cert-manager-webhook-ca True cert-manager-webhook-ca 22d
|
||||
certificate.certmanager.k8s.io/cert-manager-webhook-webhook-tls True cert-manager-webhook-webhook-tls 22d
|
||||
NAME READY SECRET AGE
|
||||
certificate.cert-manager.io/cert-manager-webhook-ca True cert-manager-webhook-ca 22d
|
||||
certificate.cert-manager.io/cert-manager-webhook-webhook-tls True cert-manager-webhook-webhook-tls 22d
|
||||
|
||||
If you do not see the CustomResourceDefinitions installed, or cannot see the
|
||||
webhook's Issuer and Certificate resources, please go back to the install guide
|
||||
|
||||
@@ -81,8 +81,8 @@ injecting the two CA bundles above into the webhook's
|
||||
ValidatingWebhookConfiguration and APIService resource in order to allow the
|
||||
Kubernetes apiserver to 'trust' the webhook apiserver.
|
||||
|
||||
This component is configured using the ``certmanager.k8s.io/inject-apiserver-ca: "true"``
|
||||
and ``certmanager.k8s.io/inject-apiserver-ca: "true"`` annotations on the
|
||||
This component is configured using the ``cert-manager.io/inject-apiserver-ca: "true"``
|
||||
and ``cert-manager.io/inject-apiserver-ca: "true"`` annotations on the
|
||||
APIService and ValidatingWebhookConfiguration resources.
|
||||
|
||||
It copies across the CA defined in the 'cert-manager-webhook-ca' Secret
|
||||
@@ -115,7 +115,7 @@ To apply the label, run:
|
||||
|
||||
.. code-block:: shell
|
||||
|
||||
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
|
||||
kubectl label namespace cert-manager cert-manager.io/disable-validation=true
|
||||
|
||||
You may need to wait a little while before cert-manager retries issuing the
|
||||
certificates if they have been failing for a while due to cert-manager's built
|
||||
|
||||
@@ -20,7 +20,7 @@ A simple CertificateRequest looks like the following:
|
||||
.. code-block:: yaml
|
||||
:linenos:
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: CertificateRequest
|
||||
metadata:
|
||||
name: my-ca-cr
|
||||
@@ -33,10 +33,10 @@ A simple CertificateRequest looks like the following:
|
||||
# We can reference ClusterIssuers by changing the kind here.
|
||||
# The default value is Issuer (i.e. a locally namespaced Issuer)
|
||||
kind: Issuer
|
||||
group: certmanager.k8s.io
|
||||
group: cert-manager.io
|
||||
|
||||
This CertificateRequest will make cert-manager attempt to make the Issuer
|
||||
``letsencrypt-prod`` in the default issuer pool ``certmanager.k8s.io``, return a
|
||||
``letsencrypt-prod`` in the default issuer pool ``cert-manager.io``, return a
|
||||
certificate based upon the certificate signing request. Other groups can be
|
||||
specified inside the ``issuerRef`` which will change the targeted issuers to other
|
||||
external, third party issuers you may have installed.
|
||||
|
||||
@@ -12,7 +12,7 @@ A simple Certificate could be defined as:
|
||||
:linenos:
|
||||
:emphasize-lines: 17-20
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: acme-crt
|
||||
@@ -97,7 +97,7 @@ expiration.
|
||||
:linenos:
|
||||
:emphasize-lines: 7,8
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example
|
||||
@@ -134,7 +134,7 @@ its private key.
|
||||
:linenos:
|
||||
:emphasize-lines: 7
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-pkcs8-cert
|
||||
|
||||
@@ -19,7 +19,7 @@ an Issuer to ``ClusterIssuer``, and removing the ``metadata.namespace`` attribut
|
||||
.. code-block:: yaml
|
||||
:emphasize-lines: 2
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: ClusterIssuer
|
||||
metadata:
|
||||
name: letsencrypt-prod
|
||||
@@ -32,7 +32,7 @@ the ``spec.issuerRef.kind`` field to ClusterIssuer:
|
||||
.. code-block:: yaml
|
||||
:emphasize-lines: 10
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: my-certificate
|
||||
|
||||
@@ -13,7 +13,7 @@ An example of an Issuer type is ACME. A simple ACME issuer could be defined as:
|
||||
:linenos:
|
||||
:emphasize-lines: 11, 16
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: letsencrypt-prod
|
||||
@@ -72,7 +72,7 @@ those credentials to perform the ACME DNS01 challenge with route53.
|
||||
:linenos:
|
||||
:emphasize-lines: 14-15
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: ClusterIssuer
|
||||
metadata:
|
||||
name: letsencrypt-prod
|
||||
|
||||
@@ -5,7 +5,7 @@ ACME-DNS
|
||||
.. code-block:: yaml
|
||||
:emphasize-lines: 10-14
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: example-issuer
|
||||
|
||||
@@ -5,7 +5,7 @@ Akamai FastDNS
|
||||
.. code-block:: yaml
|
||||
:emphasize-lines: 10-20
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: example-issuer
|
||||
|
||||
@@ -42,7 +42,7 @@ You can configure the issuer like so:
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: example-issuer
|
||||
|
||||
@@ -5,7 +5,7 @@ Cloudflare
|
||||
.. code-block:: yaml
|
||||
:emphasize-lines: 10-14
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: example-issuer
|
||||
|
||||
@@ -13,7 +13,7 @@ Handy direct link: https://cloud.digitalocean.com/account/api/tokens/new
|
||||
.. code-block:: yaml
|
||||
:emphasize-lines: 10-13
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: example-issuer
|
||||
|
||||
@@ -58,7 +58,7 @@ Next, create an Issuer (or ClusterIssuer) with a ``clouddns`` provider. An examp
|
||||
:linenos:
|
||||
:emphasize-lines: 10-16
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: example-issuer
|
||||
@@ -83,7 +83,7 @@ Once an Issuer (or ClusterIssuer) has been created successfully a Certificate ca
|
||||
:linenos:
|
||||
:emphasize-lines: 9-10
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-com
|
||||
|
||||
@@ -21,7 +21,7 @@ You can read about how the DNS01 challenge type works on the
|
||||
:linenos:
|
||||
:emphasize-lines: 12-17
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: example-issuer
|
||||
@@ -81,7 +81,7 @@ relevant `dns01` solver:
|
||||
:linenos:
|
||||
:emphasize-lines: 11
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
...
|
||||
|
||||
@@ -118,7 +118,7 @@ sufficiently, let’s focus on the provider here.
|
||||
.. code:: yaml
|
||||
:emphasize-lines: 10-16
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: example-issuer
|
||||
|
||||
@@ -87,7 +87,7 @@ Here is an example configuration for a ClusterIssuer:
|
||||
|
||||
.. code:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: ClusterIssuer
|
||||
metadata:
|
||||
name: letsencrypt-prod
|
||||
|
||||
@@ -84,7 +84,7 @@ An example of how you could configure the template is as so:
|
||||
:linenos:
|
||||
:emphasize-lines: 13-20
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: ...
|
||||
|
||||
@@ -30,7 +30,7 @@ own email address.
|
||||
:linenos:
|
||||
:emphasize-lines: 7-10, 13-14, 19
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: ClusterIssuer
|
||||
metadata:
|
||||
name: letsencrypt-staging
|
||||
@@ -101,7 +101,7 @@ along with a DNS01 solver that can be used for wildcard certificates:
|
||||
:linenos:
|
||||
:emphasize-lines: 14-15
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: ClusterIssuer
|
||||
metadata:
|
||||
name: letsencrypt-staging
|
||||
@@ -140,7 +140,7 @@ For example:
|
||||
:linenos:
|
||||
:emphasize-lines: 14-15
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: ClusterIssuer
|
||||
metadata:
|
||||
name: letsencrypt-staging
|
||||
|
||||
@@ -66,7 +66,7 @@ We can now create an Issuer referencing the Secret resource we just created:
|
||||
:linenos:
|
||||
:emphasize-lines: 8
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: ca-issuer
|
||||
@@ -88,7 +88,7 @@ desired certificate. You can read more about the Certificate resource in
|
||||
:linenos:
|
||||
:emphasize-lines: 9, 10, 11, 12
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-com
|
||||
|
||||
@@ -15,7 +15,7 @@ created with a resource like so:
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: ClusterIssuer
|
||||
metadata:
|
||||
name: selfsigning-issuer
|
||||
@@ -31,7 +31,7 @@ referencing the newly created Issuer in your ``issuerRef``:
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-crt
|
||||
|
||||
@@ -46,7 +46,7 @@ We can now create a cluster issuer referencing this secret:
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: vault-issuer
|
||||
@@ -83,7 +83,7 @@ Once we have created the above Issuer we can use it to obtain a certificate.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-com
|
||||
@@ -147,7 +147,7 @@ We can now create an issuer referencing this secret:
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: vault-issuer
|
||||
@@ -176,7 +176,7 @@ Once we have created the above Issuer we can use it to obtain a certificate.
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-com
|
||||
|
||||
@@ -65,7 +65,7 @@ Save the below content after making your amendments to a file named
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: cloud-venafi-issuer
|
||||
@@ -142,7 +142,7 @@ Save the below content after making your amendments to a file named
|
||||
|
||||
.. code-block:: yaml
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: tpp-venafi-issuer
|
||||
|
||||
@@ -28,7 +28,7 @@ DNS names that is valid for 90d and renews 15d before expiry is below:
|
||||
:linenos:
|
||||
:emphasize-lines: 9, 10, 11, 12
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-com
|
||||
|
||||
@@ -22,7 +22,7 @@ as described on the Ingress exists. For example:
|
||||
metadata:
|
||||
annotations:
|
||||
# add an annotation indicating the issuer to use.
|
||||
certmanager.k8s.io/cluster-issuer: nameOfClusterIssuer
|
||||
cert-manager.io/cluster-issuer: nameOfClusterIssuer
|
||||
name: myIngress
|
||||
namespace: myIngress
|
||||
spec:
|
||||
@@ -67,11 +67,11 @@ Supported annotations
|
||||
You can specify the following annotations on ingresses in order to trigger
|
||||
Certificate resources to be automatically created:
|
||||
|
||||
* ``certmanager.k8s.io/issuer`` - the name of an Issuer to acquire the
|
||||
* ``cert-manager.io/issuer`` - the name of an Issuer to acquire the
|
||||
certificate required for this ingress from. The Issuer **must** be in the same
|
||||
namespace as the Ingress resource.
|
||||
|
||||
* ``certmanager.k8s.io/cluster-issuer`` - the name of a ClusterIssuer to acquire
|
||||
* ``cert-manager.io/cluster-issuer`` - the name of a ClusterIssuer to acquire
|
||||
the certificate required for this ingress from. It does not matter which
|
||||
namespace your Ingress resides, as ClusterIssuers are non-namespaced resources.
|
||||
|
||||
@@ -79,7 +79,7 @@ Certificate resources to be automatically created:
|
||||
configuration of the ingress-shim (see above). Namely, a default issuer must be
|
||||
specified as arguments to the ingress-shim container.
|
||||
|
||||
* ``certmanager.k8s.io/acme-http01-ingress-class`` - this annotation allows you
|
||||
* ``acme.cert-manager.io/http01-ingress-class`` - this annotation allows you
|
||||
to configure ingress class that will be used to solve challenges for this
|
||||
ingress. Customising this is useful when you are trying to secure internal
|
||||
services, and need to solve challenges using different ingress class to that
|
||||
@@ -87,7 +87,7 @@ Certificate resources to be automatically created:
|
||||
annotation is not set, this defaults to the ingress class of the ingress
|
||||
resource.
|
||||
|
||||
* ``certmanager.k8s.io/acme-http01-edit-in-place: "true"`` - this controls
|
||||
* ``acme.cert-manager.io/http01-edit-in-place: "true"`` - this controls
|
||||
whether the ingress is modified 'in-place', or a new one created specifically
|
||||
for the http01 challenge. If present, and set to "true" the existing ingress
|
||||
will be modified. Any other value, or the absence of the annotation assumes
|
||||
|
||||
@@ -44,7 +44,7 @@ version number you want to install:
|
||||
# If you are upgrading from v0.5 or below, you should manually add this
|
||||
# label to your cert-manager namespace to ensure the `webhook component`_
|
||||
# can provision correctly.
|
||||
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
|
||||
kubectl label namespace cert-manager cert-manager.io/disable-validation=true
|
||||
|
||||
helm upgrade --version <version> <release_name> jetstack/cert-manager
|
||||
|
||||
@@ -74,7 +74,7 @@ version number you want to install:
|
||||
# If you are upgrading from v0.5 or below, you should manually add this
|
||||
# label to your cert-manager namespace to ensure the `webhook component`_
|
||||
# can provision correctly.
|
||||
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
|
||||
kubectl label namespace cert-manager cert-manager.io/disable-validation=true
|
||||
|
||||
kubectl apply \
|
||||
-f https://github.com/jetstack/cert-manager/releases/download/<version>/cert-manager.yaml
|
||||
|
||||
@@ -21,7 +21,7 @@ You can read more about the Issuer resource in the :doc:`Issuer reference docs <
|
||||
.. code-block:: yaml
|
||||
:linenos:
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: letsencrypt-staging
|
||||
@@ -86,7 +86,7 @@ Once we have created the above Issuer we can use it to obtain a certificate.
|
||||
.. code-block:: yaml
|
||||
:linenos:
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-com
|
||||
|
||||
@@ -18,7 +18,7 @@ You can read more about the Issuer resource in the :doc:`Issuer reference docs <
|
||||
.. code-block:: yaml
|
||||
:linenos:
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: letsencrypt-staging
|
||||
@@ -60,7 +60,7 @@ Once we have created the above Issuer we can use it to obtain a certificate.
|
||||
.. code-block:: yaml
|
||||
:linenos:
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-com
|
||||
|
||||
@@ -146,7 +146,7 @@ Create a file named ``cluster-issuer.yaml``:
|
||||
:linenos:
|
||||
:emphasize-lines: 11
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: ClusterIssuer
|
||||
metadata:
|
||||
# Adjust the name here accordingly
|
||||
|
||||
@@ -4,7 +4,7 @@ metadata:
|
||||
name: kuard
|
||||
annotations:
|
||||
kubernetes.io/ingress.class: "nginx"
|
||||
certmanager.k8s.io/issuer: "letsencrypt-prod"
|
||||
cert-manager.io/issuer: "letsencrypt-prod"
|
||||
|
||||
spec:
|
||||
tls:
|
||||
|
||||
@@ -4,7 +4,7 @@ metadata:
|
||||
name: kuard
|
||||
annotations:
|
||||
kubernetes.io/ingress.class: "nginx"
|
||||
certmanager.k8s.io/issuer: "letsencrypt-staging"
|
||||
cert-manager.io/issuer: "letsencrypt-staging"
|
||||
|
||||
spec:
|
||||
tls:
|
||||
|
||||
@@ -4,7 +4,7 @@ metadata:
|
||||
name: kuard
|
||||
annotations:
|
||||
kubernetes.io/ingress.class: "nginx"
|
||||
#certmanager.k8s.io/issuer: "letsencrypt-staging"
|
||||
#cert-manager.io/issuer: "letsencrypt-staging"
|
||||
|
||||
spec:
|
||||
tls:
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: letsencrypt-prod
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: letsencrypt-staging
|
||||
|
||||
@@ -410,7 +410,7 @@ Once edited, apply the custom resource:
|
||||
.. code-block:: shell
|
||||
|
||||
$ kubectl create --edit -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.10/docs/tutorials/acme/quick-start/example/staging-issuer.yaml
|
||||
issuer.certmanager.k8s.io "letsencrypt-staging" created
|
||||
issuer.cert-manager.io "letsencrypt-staging" created
|
||||
|
||||
Also create a production issuer and deploy it. As with the staging issuer, you
|
||||
will need to update this example and add in your own email address.
|
||||
@@ -426,7 +426,7 @@ will need to update this example and add in your own email address.
|
||||
.. code-block:: shell
|
||||
|
||||
$ kubectl create --edit -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.10/docs/tutorials/acme/quick-start/example/production-issuer.yaml
|
||||
issuer.certmanager.k8s.io "letsencrypt-prod" created
|
||||
issuer.cert-manager.io "letsencrypt-prod" created
|
||||
|
||||
Both of these issuers are configured to use the
|
||||
:doc:`HTTP01 </tasks/issuers/setup-acme/http01/index>` challenge provider.
|
||||
@@ -441,15 +441,15 @@ Check on the status of the issuer after you create it:
|
||||
Name: letsencrypt-staging
|
||||
Namespace: default
|
||||
Labels: <none>
|
||||
Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"certmanager.k8s.io/v1alpha2","kind":"Issuer","metadata":{"annotations":{},"name":"letsencrypt-staging","namespace":"default"},"spec":{"a...
|
||||
API Version: certmanager.k8s.io/v1alpha2
|
||||
Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"cert-manager.io/v1alpha2","kind":"Issuer","metadata":{"annotations":{},"name":"letsencrypt-staging","namespace":"default"},"spec":{"a...
|
||||
API Version: cert-manager.io/v1alpha2
|
||||
Kind: Issuer
|
||||
Metadata:
|
||||
Cluster Name:
|
||||
Creation Timestamp: 2018-11-17T18:03:54Z
|
||||
Generation: 0
|
||||
Resource Version: 9092
|
||||
Self Link: /apis/certmanager.k8s.io/v1alpha2/namespaces/default/issuers/letsencrypt-staging
|
||||
Self Link: /apis/cert-manager.io/v1alpha2/namespaces/default/issuers/letsencrypt-staging
|
||||
UID: 25b7ae77-ea93-11e8-82f8-42010a8a00b5
|
||||
Spec:
|
||||
Acme:
|
||||
@@ -537,7 +537,7 @@ certificate object. You can view this information using the
|
||||
Namespace: default
|
||||
Labels: <none>
|
||||
Annotations: <none>
|
||||
API Version: certmanager.k8s.io/v1alpha2
|
||||
API Version: cert-manager.io/v1alpha2
|
||||
Kind: Certificate
|
||||
Metadata:
|
||||
Cluster Name:
|
||||
@@ -551,7 +551,7 @@ certificate object. You can view this information using the
|
||||
Name: kuard
|
||||
UID: a3e9f935-ea87-11e8-82f8-42010a8a00b5
|
||||
Resource Version: 9295
|
||||
Self Link: /apis/certmanager.k8s.io/v1alpha2/namespaces/default/certificates/quickstart-example-tls
|
||||
Self Link: /apis/cert-manager.io/v1alpha2/namespaces/default/certificates/quickstart-example-tls
|
||||
UID: 68d43400-ea92-11e8-82f8-42010a8a00b5
|
||||
Spec:
|
||||
Dns Names:
|
||||
@@ -593,11 +593,11 @@ use the describe command as well to see some details:
|
||||
|
||||
Name: quickstart-example-tls
|
||||
Namespace: default
|
||||
Labels: certmanager.k8s.io/certificate-name=quickstart-example-tls
|
||||
Annotations: certmanager.k8s.io/alt-names=example.your-domain.com
|
||||
certmanager.k8s.io/common-name=example.your-domain.com
|
||||
certmanager.k8s.io/issuer-kind=Issuer
|
||||
certmanager.k8s.io/issuer-name=letsencrypt-staging
|
||||
Labels: cert-manager.io/certificate-name=quickstart-example-tls
|
||||
Annotations: cert-manager.io/alt-names=example.your-domain.com
|
||||
cert-manager.io/common-name=example.your-domain.com
|
||||
cert-manager.io/issuer-kind=Issuer
|
||||
cert-manager.io/issuer-name=letsencrypt-staging
|
||||
|
||||
Type: kubernetes.io/tls
|
||||
|
||||
@@ -646,7 +646,7 @@ certificate.
|
||||
Namespace: default
|
||||
Labels: <none>
|
||||
Annotations: <none>
|
||||
API Version: certmanager.k8s.io/v1alpha2
|
||||
API Version: cert-manager.io/v1alpha2
|
||||
Kind: Certificate
|
||||
Metadata:
|
||||
Cluster Name:
|
||||
@@ -660,7 +660,7 @@ certificate.
|
||||
Name: kuard
|
||||
UID: a3e9f935-ea87-11e8-82f8-42010a8a00b5
|
||||
Resource Version: 283686
|
||||
Self Link: /apis/certmanager.k8s.io/v1alpha2/namespaces/default/certificates/quickstart-example-tls
|
||||
Self Link: /apis/cert-manager.io/v1alpha2/namespaces/default/certificates/quickstart-example-tls
|
||||
UID: bdd93b32-ea97-11e8-82f8-42010a8a00b5
|
||||
Spec:
|
||||
Dns Names:
|
||||
|
||||
@@ -282,7 +282,7 @@ Save the following YAML into a file named ``venafi-issuer.yaml``:
|
||||
.. code-block:: yaml
|
||||
:linenos:
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: venafi-issuer
|
||||
@@ -349,7 +349,7 @@ Save the following YAML into a file named ``venafi-issuer.yaml``:
|
||||
.. code-block:: yaml
|
||||
:linenos:
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Issuer
|
||||
metadata:
|
||||
name: venafi-issuer
|
||||
@@ -409,7 +409,7 @@ For now, we will create a basic x509 Certificate that is valid for our domain,
|
||||
.. code-block:: yaml
|
||||
:linenos:
|
||||
|
||||
apiVersion: certmanager.k8s.io/v1alpha2
|
||||
apiVersion: cert-manager.io/v1alpha2
|
||||
kind: Certificate
|
||||
metadata:
|
||||
name: example-com-tls
|
||||
|
||||
Reference in New Issue
Block a user