From f587616e0aadbb50941b319744145bfaba3bfdf0 Mon Sep 17 00:00:00 2001 From: Ashley Davis Date: Thu, 5 Sep 2024 12:42:16 +0100 Subject: [PATCH] update note on commonName field See #1474 Signed-off-by: Ashley Davis --- content/docs/usage/certificate.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/docs/usage/certificate.md b/content/docs/usage/certificate.md index 524ba5fe554..93b2bf0a960 100644 --- a/content/docs/usage/certificate.md +++ b/content/docs/usage/certificate.md @@ -83,8 +83,9 @@ spec: subject: organizations: - jetstack - # The use of the common name field has been deprecated since 2000 and is - # discouraged from being used. + # Avoid using commonName for end-entity certificates for DNS names. Unless you have a specific + # need for it in your environment, use dnsNames exclusively to avoid the issues with commonName. + # Most commonly, commonName is used to give human-readable names to CA certificates. commonName: example.com # The literalSubject field is exclusive with subject and commonName. It allows