Clarify domain stubbing parts (#7796)

This commit is contained in:
Simon Alling 2020-07-28 17:08:44 +02:00 committed by GitHub
parent d6457aac63
commit 8528095c20
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

@ -106,13 +106,13 @@ To provide a similar setup for services from remote clusters, you name
services from remote clusters in the format services from remote clusters in the format
`<name>.<namespace>.global`. Istio also ships with a CoreDNS server that `<name>.<namespace>.global`. Istio also ships with a CoreDNS server that
will provide DNS resolution for these services. In order to utilize this will provide DNS resolution for these services. In order to utilize this
DNS, Kubernetes' DNS must be configured to `stub a domain` for `.global`. DNS, Kubernetes' DNS must be configured to *stub a domain* for `.global`.
{{< warning >}} {{< warning >}}
Some cloud providers have different specific `DNS domain stub` capabilities Some cloud providers have different specific DNS domain stub capabilities
and procedures for their Kubernetes services. Reference the cloud provider's and procedures for their Kubernetes services. Reference the cloud provider's
documentation to determine how to `stub DNS domains` for each unique documentation to determine how to stub DNS domains for each unique
environment. The objective of this bash is to stub a domain for `.global` on environment. The objective here is to stub a domain for `.global` on
port `53` to reference or proxy the `istiocoredns` service in Istio's service port `53` to reference or proxy the `istiocoredns` service in Istio's service
namespace. namespace.
{{< /warning >}} {{< /warning >}}