Armory

CD-as-a-Service now supports using the Istio service mesh, which allows you to implement precise control over the exact percentage of traffic received by the next version of your app. When you use a pod-ratio canary strategy, you can only approximately control the correct traffic split. When you use Istio, however, you can achieve fine-grained traffic control over your canary deployments.

To integrate Istio with CD-as-a-Service, add the traffic management block as a top-level field in your deployment config file and provide the Istio resource names.

Check out [Traffic Management Using Istio](https://docs.armory.io/cd-as-a-service/concepts/deployment/traffic-management/istio/) and [Configure Traffic Management Using Istio](https://docs.armory.io/cd-as-a-service/tasks/deploy/traffic-management/istio/) for details.

```yaml
trafficManagement:
  - targets: [staging]
    istio:
      - virtualService:
          name: istio-sample-vs
        destinationRule:
          name: istio-sample-dr
```

Canary Deployments Can Now Use Istio Service Mesh