Fix rendering of example federated service DNS name (#9161)

This commit is contained in:
Alex Robinson
2018-06-24 21:18:03 -05:00
committed by k8s-ci-robot
parent e2adcde55d
commit bad6ab958d
@@ -268,12 +268,13 @@ With the introduction of Federated Services and Cross-Cluster Service
Discovery, this concept is extended to cover Kubernetes services Discovery, this concept is extended to cover Kubernetes services
running in any other cluster across your Cluster Federation, globally. running in any other cluster across your Cluster Federation, globally.
To take advantage of this extended range, you use a slightly different To take advantage of this extended range, you use a slightly different
DNS name (of the form "<servicename>.<namespace>.<federationname>", DNS name of the form ```"<servicename>.<namespace>.<federationname>"```
e.g. myservice.mynamespace.myfederation) to resolve Federated to resolve Federated Services. For example, you might use
Services. Using a different DNS name also avoids having your existing `myservice.mynamespace.myfederation`. Using a different DNS name also
applications accidentally traversing cross-zone or cross-region avoids having your existing applications accidentally traversing
networks and you incurring perhaps unwanted network charges or cross-zone or cross-region networks and you incurring perhaps unwanted
latency, without you explicitly opting in to this behavior. network charges or latency, without you explicitly opting in to this
behavior.
So, using our NGINX example service above, and the Federated Service So, using our NGINX example service above, and the Federated Service
DNS name form just described, let's consider an example: A Pod in a DNS name form just described, let's consider an example: A Pod in a