content/en/docs/reference/config/analysis/ist0109/index.md
This message occurs when Istio detects an overlap between virtual service resources that conflict with one another. For example, multiple virtual services defined to use the same hostname and attached to a mesh gateway will generate an error message. Note that Istio supports merging of virtual services that are attached to the ingress gateways.
To resolve this issue, you can take one of the following actions:
exportTo field.The productpage virtual service in namespace team1 conflicts with the
custom virtual service in team2 namespace because both of the following
are true:
productpage.default.svc.cluster.local.{{< text yaml >}} apiVersion: networking.istio.io/v1 kind: VirtualService metadata: name: productpage namespace: team-1 spec: hosts:
apiVersion: networking.istio.io/v1 kind: VirtualService metadata: name: custom namespace: team-2 spec: hosts:
{{< /text >}}
You can resolve this issue by setting the exportTo field to . so
that each virtual service is scoped only to its own namespace:
{{< text yaml >}} apiVersion: networking.istio.io/v1 kind: VirtualService metadata: name: productpage namespace: team-1 spec: exportTo:
apiVersion: networking.istio.io/v1 kind: VirtualService metadata: name: custom namespace: team-2 spec: exportTo:
{{< /text >}}