diff --git a/docs/reference/ingress-shim.rst b/docs/reference/ingress-shim.rst index a9358d38c..dd56f8d34 100644 --- a/docs/reference/ingress-shim.rst +++ b/docs/reference/ingress-shim.rst @@ -5,7 +5,7 @@ ingress-shim cert-manager can be configured to automatically provision TLS certificates for Ingress resources via annotations on your Ingresses. -A small sub-component of cert-manager, ingress-shim_ is responsible for this. +A small sub-component of cert-manager, ingress-shim, is responsible for this. How it works ============ @@ -32,7 +32,8 @@ when deploying using Helm: .. code-block:: shell - --set ingressShim.extraArgs='{--default-issuer-name=letsencrypt-prod,--default-issuer-kind=ClusterIssuer}' + --set ingressShim.defaultIssuerName=letsencrypt-prod \ + --set ingressShim.defaultIssuerKind=ClusterIssuer In the above example, cert-manager will create Certificate resources that reference the ClusterIssuer `letsencrypt-prod` for all Ingresses that have a ``kubernetes.io/tls-acme: "true"`` annotation. @@ -76,4 +77,3 @@ Certificate resources to be automatically created: annotation assumes "false". .. _kube-lego: https://github.com/jetstack/kube-lego -.. _ingress-shim: https://github.com/jetstack/cert-manager/tree/master/cmd/ingress-shim diff --git a/docs/tutorials/acme/migrating-from-kube-lego.rst b/docs/tutorials/acme/migrating-from-kube-lego.rst index cab2c2767..8f3850f5f 100644 --- a/docs/tutorials/acme/migrating-from-kube-lego.rst +++ b/docs/tutorials/acme/migrating-from-kube-lego.rst @@ -223,7 +223,8 @@ ClusterIssuer ``letsencrypt-staging`` (as above), run: helm upgrade cert-manager \ stable/cert-manager \ --namespace kube-system \ - --set ingressShim.extraArgs='{--default-issuer-name=letsencrypt-staging,--default-issuer-kind=ClusterIssuer}' + --set ingressShim.defaultIssuerName=letsencrypt-staging \ + --set ingressShim.defaultIssuerKind=ClusterIssuer You should see the cert-manager pod be re-created, and once started it should automatically create Certificate resources for all of your ingresses that