[BUG]admiral can not access to remote cluster

[ZBYuan0813]

Describe the bug I deployment admiral and istio as the example, but when I access stage.greeting.global, I can only access to local cluster.

Steps To Reproduce 1.create cluster with kind and label cluster1 node with us-west-2, cluster2 node with us-east-2. 2.depoy istio mutli-primary and enable dns. 3. deploy admiral 4. access stage.greeting.blobal through webapp pod. Expected behavior I can only access to local cluster. The serviceEntry as follow:

apiVersion: networking.istio.io/v1beta1
kind: ServiceEntry
metadata:
  annotations:
    app.kubernetes.io/created-by: admiral
  creationTimestamp: "2022-09-27T02:04:37Z"
  generation: 14
  labels:
    identity: greeting
  name: stage.greeting.global-se
  namespace: admiral-sync
  resourceVersion: "722821"
  uid: ecd8eafe-f75d-4bdf-af4f-5b9e6ec1a8e1
spec:
  addresses:
  - 240.0.10.1
  endpoints:
  - address: greeting.sample.svc.cluster.local
    locality: us-west-2
    ports:
      http: 80
  - address: 172.18.255.201
    locality: us-east-2
    ports:
      http: 15443
  hosts:
  - stage.greeting.global
  location: MESH_INTERNAL
  ports:
  - name: http
    number: 80
    protocol: http
  resolution: DNS

172.18.255.201 is the cluster2 eastwestgateway lb ip.

The response for curl stage.greeting.global

/ # curl  stage.greeting.global
Hello World! - Admiral!!/ #
/ # curl  stage.greeting.global
Hello World! - Admiral!!/ #
/ # curl  stage.greeting.global
Hello World! - Admiral!!/ #
/ # curl  stage.greeting.global
/ # curl  stage.greeting.global
Hello World! - Admiral!!/ #
/ # curl  stage.greeting.global
Hello World! - Admiral!!/ #