kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #24285 from psykulsk/patch-1 

Fix Common Name in Ingress TLS docs to match the name used in example.
pull/24329/head
Kubernetes Prow Robot 2020-10-01 08:34:54 -07:00 committed by GitHub
parent 6f1ec1936f 996f433b92
commit 33f77f080b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/concepts/services-networking/ingress.md
View File

@ -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" >}}