VirtualService host merging unavailability in sidecars

1

I’ve read that

A VirtualService can only be fragmented this way if it is bound to a gateway. Host merging is not supported in sidecars.

in the deployment guide after seeing “multiple entries for domain” error across sidecars in the cluster.

To clarify, does this mean that two VirtualService definitions need to be made for a service that exposed both internally and through ingress Gateway — with one VirtualService using host & gateways bindings to set a domain it can be accessed on (without specifying mesh Gateway) and another VirtualService only specifying servicename host and mesh Gateway for internal availability?

2

A little late, but i’m having problems with that too…

I think it means as long as multiple VirtualService use the same host entry, they will not merge in the sidecar, but the last one will overwrite the others and remain the only active VirtualService.

Did you solve your problem ?

I feel this is a pretty standard use case, because we have to have the same service running in different versions in our backend like this

https://sameservice.domain.com/v1
https://sameservice.domain.com/v2
https://sameservice.domain.com/v3

and use prefix matching and destinationrule todo the routing…

…and this works on the ingress-gateway, so why not in the sidecar ? :frowning:

3

Watch this issue… maybe we can get merging in sidecars at some point :slight_smile: