Argo Rollouts 1.3 Pre-Release

Update Sep 19th 2022: Argo Rollouts 1.3 Release is now live here:
https://github.com/argoproj/argo-rollouts/releases/tag/v1.3.0

Argo Rollouts 1.3 is around the corner! At this point we are publishing the release candidate, making available some community acclaimed feature requests. It has been about 4 months since Argo Rollouts 1.2 came out, and we are pleased to welcome 11 first time contributors for this new milestone. Check below for more details about the new features.

Photo by Joey Kyber on Unsplash

Header Based Routing (Istio)

Argo Rollouts has a new step in the rollouts resource called setHeaderRoute to allow users to match on specific request headers to send traffic to the canary pods. This is an example on how to match on the exact header value:

apiVersion: argoproj.io/v1alpha1
kind: Rollout
spec:
  ...
  strategy:
    canary:
      canaryService: canary-service
      stableService: stable-service
      trafficRouting:
        managedRoutes:
          - name: my-rollouts-managed-route
            istio:
              virtualService:
                name: rollouts-demo-vsvc
        steps:
        - setHeaderRoute:
          name: "my-rollouts-managed-route"
          match:
            - headerName: Some-Header
              headerValue:
                exact: Mozilla

Argo Rollouts will use the information provided in the setHeaderRoute to properly configure the traffic router in use (Istio in this case) to behave according to what is specified. In the example above it will configure Istio adding a new managed route (my-rollouts-managed-route) in the virtual service (rollouts-demo-vsvc) to only send traffic to the canary service (canary-service) when the income request header with name “Some-Header” matches the exact value of “Mozilla”.

Please refer to the documentation to learn more about the new setHeaderRoute step and understand how to define more powerful matchers.

The new setHeaderRoute step is at this point only implemented when used with Istio but can be integrated with any other traffic router that supports header based routing. We welcome and will support contributors willing to implement this feature to additional traffic routers.

Thanks to Andrii Perenesenko (Intuit) for implementing this new feature.

Traffic Mirroring (Istio)

Similarly to the Header Based routing, the new Traffic Mirroring feature also defines a new step called setMirrorRoute in the Rollout resource to configure how to mirror traffic to the canary service.

apiVersion: argoproj.io/v1alpha1
kind: Rollout
spec:
  ...
  strategy:
    canary:
      canaryService: canary-service
      stableService: stable-service
      trafficRouting:
        managedRoutes:
          - name: mirror-route
        istio:
          virtualService:
            name: rollouts-demo-vsvc
      steps:
      - setMirrorRoute:
          name: mirror-route
          percentage: 35
          match:
            - method:
                exact: GET
              path:
                prefix: /

In the example above, Argo Rollouts will mirror 35% of the traffic of incoming GET requests with / prefix to the canary service.

Please refer to the main documentation to learn how to provide different matchers to mirror your application’s traffic.

Traffic Mirroring is currently only implemented for Istio and again, community contributions are more than welcome to support additional traffic routers.

Big thanks to Zach Aller (Intuit) for implementing this new feature and driving the new API design with the community.

Traefik Routing Support

Argo Rollouts now ships with support for Traefik in canary deployments.

apiVersion: argoproj.io/v1alpha1
kind: Rollout
spec:
  strategy:
    canary:
      trafficRouting:
        traefik:
          weightedTraefikServiceName: traefik-service
    ...

Defining Traefik is as simple as in the example above. Please refer to the main documentation to learn more about the Traefik support.

Thanks to the new contributor Philipp Plotnikov (Codefresh) for this great feature!

Other Notable Features

Dashboard Improvements

Argo Rollouts dashboard has been enhanced to provide more information in the UI, showing users the details of analysis runs. The canary scale box can also be expanded to show more details.

You can check out more screenshots in the original pull requests:

• Dashboard displaying the setCanaryScale values (#1923)
• Dashboard now displaying analysis details (#1910)

Thanks to Sai Sindhu Chakradari (Intuit) for driving these UI improvements.

InfluxDB Metric Provider Support

It is now possible to use InfluxDB as a metric provider during Argo Rollouts analysis. Check the main documentation for more details about how to use this feature.

Thanks to jaymebrd (InfluxData) for driving this implementation.

We would like to thank for all contributors who participated in this new milestone. For a full list of contributors, features and bug fixes please refer to the release page in Github where you can also find details about how to install and give this new version a try.

It would be great if we could receive feedback from the community about this pre-release to allow us to address any potential issues and be ready for 1.3.0. If you want to provide feedback please feel free to open an issue in Argo Rollouts github repo.