Istio Virtual Service Redirect. With this configuration all the traffic that exit the virtual machine to a k8s service will pass the envoy process and will enter the istio service mash. The forwarding target can be one of several versions of a service (see glossary in beginning of document).
Remove the service entry and virtual service previously deployed in this guide. Exporting a virtual service allows it to be used by sidecars and gateways defined in other namespaces. Unlike the virtual service’s host, the destination’s host must be a real destination that exists in the red hat openshift service mesh service registry.
Istio’s service registry is composed of all.
A value of '*' indicates it is reachable within the mesh '.' indicates it is reachable within its namespace. This works but falls a little short when it comes to directing traffic between different versions of upstream apis. 5601 and grafana with port:3000. The destination.host should unambiguously refer to a service in the service registry.