Progressive Delivery with the Kubernetes Gateway API

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 Kubernetes Gateway API

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.

Prerequisites

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.

How to use the Gateway API with Argo Rollouts

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 an HTTPRoute
6. Create canary and stable services
7. Create your Rollout 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 several other implementations at the provider status page or try our quick start guide.