From 73780ca1bd90e1af97f71c86074012a108f47011 Mon Sep 17 00:00:00 2001 From: Vladimir Masarik Date: Fri, 28 Aug 2020 15:31:39 +0200 Subject: [PATCH] Updated ingress.md TLS section --- content/en/docs/concepts/services-networking/ingress.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md index 7743ae656a..3977cbc233 100644 --- a/content/en/docs/concepts/services-networking/ingress.md +++ b/content/en/docs/concepts/services-networking/ingress.md @@ -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 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" >}} {{< note >}}