A central advantage of traffic management in Istio is that it allows dynamic request routing. Some common applications for dynamic request routing include canary deployments and blue/green deployments. The two key resources in Istio traffic management are virtual services and destination rules.
- Virtual services intercept and direct traffic to your Kubernetes services, allowing you to divide percentages of traffic from a request to different services. You can use them to define a set of routing rules to apply when a host is addressed.
- Destination rules serve as the single source of truth about which service versions are available to receive traffic from virtual services. You can use these resources to define policies that apply to traffic that is intended for a service after routing has occurred.
This section describes how to add an example virtual service that corresponds to the
reviews microservice in the sample BookInfo app. The purpose of this service is to divide traffic between two versions of the
In this example, we take the traffic to the
reviews service and intercept it so that 50 percent of it goes to
v1 of the service and 50 percent goes to
After this virtual service is deployed, we will generate traffic and see from the Kiali visualization that traffic is being routed evenly between the two versions of the service.
To deploy the virtual service and destination rules for the
- Go to the project view and click Import YAML.
- Copy resources below into the form.
- Click Import.
- name: v1
- name: v2
- name: v3
Result: When you generate traffic to this service (for example, by refreshing the ingress gateway URL), the Kiali traffic graph will reflect that traffic to the
reviews service is divided evenly between