Code:

Social:

Argo Rollouts is a progressive delivery controller for Kubernetes. It supports several advanced deployment methods such as blue/green and canaries. For canary deployments Argo Rollouts can optionally use a traffic provider to split traffic between pods with full control and in a gradual way.

Until recently adding a new traffic provider to Argo Rollouts needed ad-hoc support code. With the adoption of the Gateway API, the integration becomes much easier as any traffic provider that implements the API will automatically be supported by Argo Rollouts.

The Gateway API is an open source project managed by the SIG-NETWORK community. It is a collection of resources that model service networking in Kubernetes.

See a list of current projects that support the API.

You need the following

1. A Kubernetes cluster
2. An installation of the Argo Rollouts controller
3. A traffic provider that supports the Gateway API
4. An installation of the Gateway plugin

Once everything is ready you need to create a Rollout resource for all workloads that will use the integration.

This is the installation process.

1. Enable Gateway Provider and create Gateway entrypoint
2. Create GatewayClass and Gateway resources
3. Create cluster entrypoint and map it with our Gateway entrypoint
4. Install Argo Rollouts in your cluster along with the Gateway API plugin
5. Create HTTPRoute
6. Create canary and stable services
7. Create argo-rollouts resources
8. Start a deployment

The first 3 steps are specific to your provider/implementation of the Gateway API inside the Kubernetes cluster. The rest of the steps are the same regardless of the specific implementation you chose.

See end-to-end examples for:

• Cilium
• EnvoyGateway
• Gloo Gateway
• Google Cloud
• Kong
• NGINX Kubernetes Gateway
• Traefik

Note that these examples are included just for illustration purposes. You should be able to use any solution that implements the Gateway API.

There are many ways to install the Gateway API plugin in Argo Rollouts. The easiest one is to simply download it during startup.

apiVersion: v1
kind: ConfigMap
metadata:
  name: argo-rollouts-config # must be so name
  namespace: argo-rollouts # must be in this namespace
data:
  trafficRouterPlugins: |-
    - name: "argoproj-labs/gatewayAPI"
      location: "https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi/releases/download/v0.0.0-rc1/gateway-api-plugin-linux-amd64"

Deploy this file with kubectl or Argo CD or any other deployment method you use for your cluster.

For more details see the Plugin documentation at Argo Rollouts.

The gateway API plugin should cover all providers that support it. If you find an issue please tell us about it

If you also want to add an example with your favorite gateway API provider please send us a Pull Request.