Deploy the same version service in multiple clusters

[yuchen9459]

Describe the feature request
Deploy the same version service in multiple clusters using gateway connected feature and make sure they can be accessed

Describe alternatives you've considered
In the Version Routing in a Multicluster Service Mesh tutorial , it deploys two version of review services in the second cluster. I created three Kubernetes clusters and deploy review-v1 in cluster1, review-v2 and review-v3 in cluster2 and cluster 3.

I wonder how can I deploy the same version service like review-v2 in two clusters and make sure both of them can be accessed.
Currently, I have tried to add some lines to the deployment files:

apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: reviews-default
spec:
  hosts:
  - reviews.default.global
  location: MESH_INTERNAL
  ports:
  - name: http1
    number: 9080
    protocol: http
  resolution: DNS
  addresses:
  - 127.255.0.3
  endpoints:
  - address: 172.17.0.3
    labels:
      cluster: cluster2
    ports:
      http1: 30417  # Do not change this port value
  - address: 172.17.0.4
    labels:
      cluster: cluster3
    ports:
      http1: 31940
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: reviews-global
spec:
  host: reviews.default.global
  trafficPolicy:
    tls:
      mode: ISTIO_MUTUAL
  subsets:
  - name: v2
    labels:
      cluster: cluster3
      cluster: cluster2
   - name: v3
    labels:
      cluster: cluster2
      cluster: cluster3

As you can see from the yaml file, I added two endpoints for the ServiceEntry review-default. Since one subsets cannot have two labels, the second label in the configuration file will overwrite the first one. After deployment, v2 subset's corresponding label is cluster2, and v3 subset's corresponding label is cluster3. Therefore, after the deployment, all requests for a certain service will be directed to a cluster instead of two-clusters in a certain order (such as round-robin).

[hzxuzhonghu]

I have investigated the gateway-connected multi-cluster model, and I think you can not create two same service in two different clusters.

[yuchen9459]

I have investigated the gateway-connected multi-cluster model, and I think you can not create two same service in two different clusters.

Thanks! If it does not work in the gateway-connected multi-cluster model, is there any other way to implement this?

[tapaskapadia]

I am also very curious how the same service with the same version that is deployed in different clusters can be both requested for depending on locality or performance using the gateway-connected multi-cluster model. I have not had any luck with similar efforts.

[istio-policy-bot]

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2020-04-07. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.