Traffic Route

This is a proposed policy not in GA yet. You can setup routing manually by leveraging the ProxyTemplate policy and the low-level Envoy configuration. Join us on Slack to share your routing requirements.

The proposed policy will enable a new TrafficRoute policy that can be used to configure both simple and more sophisticated routing rules on the traffic, like blue/green deployments and canary releases.

On Universal:

  1. type: TrafficRoute
  2. name: route-1
  3. mesh: default
  4. rules:
  5.   - sources:
  6.       - match:
  7.           service: backend
  8.     destinations:
  9.       - match:
  10.           service: redis
  11.     conf:
  12.       - weight: 90
  13.         destination:
  14.           service: redis
  15.           version: '1.0'
  16.       - weight: 10
  17.         destination:
  18.           service: redis
  19.           version: '2.0'

On Kubernetes:

  1. apiVersion: kuma.io/v1alpha1
  2. kind: TrafficRoute
  3. mesh: default
  4. metadata:
  5.   namespace: default
  6.   name: route-1
  7. spec:
  8.   rules:
  9.     - sources:
  10.       - match:
  11.           service: backend
  12.     destinations:
  13.       - match:
  14.           service: redis
  15.     conf:
  16.       - weight: 90
  17.         destination:
  18.           service: redis
  19.           version: '1.0'
  20.       - weight: 10
  21.         destination:
  22.           service: redis
  23.           version: '2.0'