Skip to content
Browse files

ExternalName warning about HTTP/TLS (#16704)

Suggested wording from sftim
  • Loading branch information...
jimmyjones2 authored and k8s-ci-robot committed Oct 9, 2019
1 parent 9cc26cf commit f835552f96ece04fb4d2a1ebdc47799b85aa9f6b
Showing with 5 additions and 0 deletions.
  1. +5 −0 content/en/docs/concepts/services-networking/
@@ -910,6 +910,11 @@ forwarding. Should you later decide to move your database into your cluster, you
can start its Pods, add appropriate selectors or endpoints, and change the
Service's `type`.

{{< warning >}}
You may have trouble using ExternalName for some common protocols, including HTTP and HTTPS. If you use ExternalName then the hostname used by clients inside your cluster is different from the name that the ExternalName references.

For protocols that use hostnames this difference may lead to errors or unexpected responses. HTTP requests will have a `Host:` header that the origin server does not recognize; TLS servers will not be able to provide a certificate matching the hostname that the client connected to.
{{< /warning >}}

{{< note >}}
This section is indebted to the [Kubernetes Tips - Part

0 comments on commit f835552

Please sign in to comment.
You can’t perform that action at this time.