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

Merge pull request #23522 from VladMasarik/patch-2 

Updated ingress.md TLS section
pull/24625/head
Kubernetes Prow Robot 2020-10-17 18:48:13 -07:00 committed by GitHub
parent 018cc1a617 73780ca1bd
commit 7abf35915d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -413,6 +413,13 @@ secure the channel from the client to the load balancer using TLS. You need to m
sure the TLS secret you created came from a certificate that contains a Common 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 `https-example.foo.com`. Name (CN), also known as a Fully Qualified Domain Name (FQDN) for `https-example.foo.com`.
{{< note >}}
Keep in mind that TLS will not work on the default rule because the
certificates would have to be issued for all the possible sub-domains. Therefore,
`hosts` in the `tls` section need to explicitly match the `host` in the `rules`
section.
{{< /note >}}
{{< codenew file="service/networking/tls-example-ingress.yaml" >}} {{< codenew file="service/networking/tls-example-ingress.yaml" >}}
{{< note >}} {{< note >}}