luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

website: clarify coredns requirement

This commit is contained in:
Mitchell Hashimoto 2018-09-25 23:37:21 -05:00
parent a69acc076d
commit add6b8e05e
No known key found for this signature in database
GPG Key ID: 744E147AA52F5B0A
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/source/docs/platform/k8s/service-sync.html.md
View File

@ -231,8 +231,11 @@ This enables external services to be discovered using native Kubernetes
tooling. This can be used to ease software migration into or out of Kubernetes, tooling. This can be used to ease software migration into or out of Kubernetes,
across platforms, to and from hosted services, and more. across platforms, to and from hosted services, and more.
-> **Requires Consul DNS in Kubernetes:** This feature requires that -> **Requires Consul DNS via CoreDNS in Kubernetes:** This feature requires that
[Consul DNS](/docs/platform/k8s/dns.html) is configured within Kubernetes. [Consul DNS](/docs/platform/k8s/dns.html) is configured within Kubernetes.
Additionally, **[CoreDNS](https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/#config-coredns)
is required (instead of kube-dns)** to resolve an
issue with resolving `externalName` services pointing to custom domains.
In the future we hope to remove this requirement by syncing the instance In the future we hope to remove this requirement by syncing the instance
addresses directly into service endpoints. addresses directly into service endpoints.