whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix CoreDNS requirement for ExternalName Service (#18566)

Browse Source
This commit is contained in:
Jan Wozniak
2020-01-11 19:19:37 +01:00
committed by Kubernetes Prow Robot
parent 03f9dd3dfd
commit 78dad3ceb6
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/service.md
+1 -1
View File
@@ -485,7 +485,7 @@ The default is `ClusterIP`.
with its value. No proxying of any kind is set up. with its value. No proxying of any kind is set up.
{{< note >}} {{< 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 >}} {{< /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. 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.
content/zh/docs/concepts/services-networking/service.md
+1 -1
View File
@@ -815,7 +815,7 @@ The default is `ClusterIP`.
with its value. No proxying of any kind is set up. with its value. No proxying of any kind is set up.
{{< note >}} {{< 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 >}} {{< /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. 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.