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 ? 