From 78dad3ceb6f5ef41efebac38b96d478d4ba723cf Mon Sep 17 00:00:00 2001 From: Jan Wozniak Date: Sat, 11 Jan 2020 19:19:37 +0100 Subject: [PATCH] Fix CoreDNS requirement for ExternalName Service (#18566) --- content/en/docs/concepts/services-networking/service.md | 2 +- content/zh/docs/concepts/services-networking/service.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index 9479d02ec8..0f3eef6081 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -485,7 +485,7 @@ The default is `ClusterIP`. with its value. No proxying of any kind is set up. {{< note >}} - You need CoreDNS version 1.7 or higher to use the `ExternalName` type. + You need either kube-dns version 1.7 or CoreDNS version 0.0.8 or higher to use the `ExternalName` type. {{< /note >}} You can also use [Ingress](/docs/concepts/services-networking/ingress/) to expose your Service. Ingress is not a Service type, but it acts as the entry point for your cluster. It lets you consolidate your routing rules into a single resource as it can expose multiple services under the same IP address. diff --git a/content/zh/docs/concepts/services-networking/service.md b/content/zh/docs/concepts/services-networking/service.md index 9ed613bf7c..121ccdfb15 100644 --- a/content/zh/docs/concepts/services-networking/service.md +++ b/content/zh/docs/concepts/services-networking/service.md @@ -815,7 +815,7 @@ The default is `ClusterIP`. with its value. No proxying of any kind is set up. {{< note >}} - You need CoreDNS version 1.7 or higher to use the `ExternalName` type. + You need either kube-dns version 1.7 or CoreDNS version 0.0.8 or higher to use the `ExternalName` type. {{< /note >}} You can also use [Ingress](/docs/concepts/services-networking/ingress/) to expose your Service. Ingress is not a Service type, but it acts as the entry point for your cluster. It lets you consolidate your routing rules into a single resource as it can expose multiple services under the same IP address.