From 996f433b9237ad1397bda40d49d4af9b8a812cdd Mon Sep 17 00:00:00 2001 From: Piotr Sykulski Date: Wed, 30 Sep 2020 23:49:20 +0200 Subject: [PATCH] Fix Common Name in Ingress TLS example to match the name used in example yaml. --- content/en/docs/concepts/services-networking/ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md index 795a3546b5e6b..7743ae656a426 100644 --- a/content/en/docs/concepts/services-networking/ingress.md +++ b/content/en/docs/concepts/services-networking/ingress.md @@ -411,7 +411,7 @@ type: kubernetes.io/tls Referencing this secret in an Ingress tells the Ingress controller to secure the channel from the client to the load balancer using TLS. You need to make sure the TLS secret you created came from a certificate that contains a Common -Name (CN), also known as a Fully Qualified Domain Name (FQDN) for `sslexample.foo.com`. +Name (CN), also known as a Fully Qualified Domain Name (FQDN) for `https-example.foo.com`. {{< codenew file="service/networking/tls-example-ingress.yaml" >}}