Striping services across clusters

Hi everyone,
I’m trying to understand, what is a recommended way for striping a service across multiple clusters in primary/remote mode?
More specifically, when a service with the same namespace/name is defined in both - primary and remote clusters, what strategy does Istio use to resolve situations, where such services aren’t identical, for example remote cluster service declares a port not declared in primary service?

1 Like