docs: xref ambient issuers in cluster-issuer docs

This commit is contained in:
Euan Kemp 2018-03-23 16:15:43 -07:00
parent 1c57feb523
commit f88707df88

View File

@ -1,4 +1,6 @@
# Creating cluster wide Issuers
# Cluster Issuers
## Creating cluster wide Issuers
cert-manager has the concept of `ClusterIssuers`. These are a non-namespaced and cluster-scoped version of an `Issuer`. The specification of a `ClusterIssuer` is exactly the same as that of an `Issuer`, but there are a couple of nuances you need to be aware of.
@ -28,6 +30,18 @@ spec:
The two manifests above define two `ClusterIssuers`. As `ClusterIssuer` resources do not specify a namespace, we must configure a namespace that cert-manager will use to store supporting resources required for each `ClusterIssuer`. We do this by specifying the `--cluster-resource-namespace` flag on the cert-manager controller. By default, this flag will be set to `kube-system`.
## Securiy of Cluster Issuers
It is assumed that cluster issuers may only be created by cluster administrators.
## Ambient Credentials
By default, a Cluster Issuer will be able to use 'ambient credentials' of the 'cert-manager' deployment for supported challenges. Currently, only the ACME DNS challenge validation makes use of ambient credentials. To learn more about this behavior, see the [ambient credentials][ambient-creds] document.
To disable this behavior, either set `--cluster-issuer-ambient-credentials=false` on cert-manager, or alternately do not create any cluster issuers which define a `spec.acme.dns01.route53` object without any associated credentials.
## Referencing Cluster Issuers
In order to reference a `ClusterIssuer` in a `Certificate` you must specify the `kind` in the `issuerRef` stanza. The following are two examples of `Certificates` that reference our `ClusterIssuers` above.
```yaml
@ -62,3 +76,6 @@ spec:
domains:
- nginx.k8s.io
```
[ambient-creds]: ambient-credentials.md