Progressive delivery in Kubernetes typically relies on percentage-based traffic splitting, but this approach can cause inconsistent user experiences during canary rollouts. Argo Rollouts combined with the Gateway API plugin and Isovalent Networking for Kubernetes (powered by Cilium) enables header-based canary routing without requiring a service mesh. The Gateway API plugin lets Argo Rollouts manage HTTPRoute resources directly, and with Gateway API 1.2's named rules support, header routes like X-Canary: true can be managed inline rather than via a separate ConfigMap. A practical demo shows how stable and canary services are configured, how a 50% weight split works, and how QA teams or internal users can be consistently routed to the canary version via HTTP header matching — all using standard Kubernetes Gateway API resources.
Table of contents
Argo Rollouts as the Release ControllerGateway API Becomes the Common Traffic LayerWhen Percentage-Based Canaries Are Not EnoughWatching It Work with Isovalent’s Gateway APIBringing It Together1.6K Impressions1 Comment