From c218139c17958a1a375ee3a120c4a8fd471f4aeb Mon Sep 17 00:00:00 2001 From: Alex Litvinenko Date: Tue, 20 Jul 2021 12:28:34 +0200 Subject: [PATCH] Adjust list of Subject Alternative Names A description of resource `Certificate` has `foo.example.com` and `bar.example.com` in the `dnsNames` section, which is different from the diagram that has `example.com` and `foo.example.com` domains. When I was looking at the schema in the article, I thought that the part related to `bar.example.com` is to follow, but it didn't and therefore was a bit confusing. --- content/en/docs/concepts/certificate.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/concepts/certificate.md b/content/en/docs/concepts/certificate.md index 2fc327e9684..e3a71c7c0cd 100644 --- a/content/en/docs/concepts/certificate.md +++ b/content/en/docs/concepts/certificate.md @@ -25,8 +25,8 @@ metadata: spec: secretName: acme-crt-secret dnsNames: + - example.com - foo.example.com - - bar.example.com issuerRef: name: letsencrypt-prod # We can reference ClusterIssuers by changing the kind here. @@ -36,8 +36,8 @@ spec: ``` This `Certificate` will tell cert-manager to attempt to use the `Issuer` named -`letsencrypt-prod` to obtain a certificate key pair for the `foo.example.com` -and `bar.example.com` domains. If successful, resulting TLS key and certificate +`letsencrypt-prod` to obtain a certificate key pair for the `example.com` +and `foo.example.com` domains. If successful, resulting TLS key and certificate will be stored in a secret named `acme-crt-secret`, with keys of `tls.key`, and `tls.crt` respectively. This secret will live in the same namespace as the `Certificate` resource.