s added to the remote cluster because <code>reviews-v3</code> is a
client of <code>ratings</code> and creating the service object creates a DNS entry. The Istio sidecar in the
<code>reviews-v3</code> pod will determine the proper <code>ratings</code> endpoint after the DNS lookup is resolved to a
service address. This would not be necessary if a multicluster DNS solution were additionally set up, e.g. as
in a federated Kubernetes environment.</p></li><li><p>Get the <code>istio-ingressgateway</code> service&