Modern application delivery is filled with pitfalls: version transitions, traffic management, performance monitoring, and rollback mechanisms. If you encounter a problem during an upgrade, what can you do? Mirror traffic? Debug locally? Roll back?

A common Gateway API enables any provider to support Argo Rollouts without any custom ad-hoc code. ArgoCD monitors Prometheus metrics to verify the performance of a new version and reverts to the previous version if the metrics don't meet success criteria.

This hands-on lab will guide you on how to integrate Argo Rollouts with applications running different Gateway API implementations. Utilizing ArgoCD and Gateway API resources (HTTPRoute), you’ll learn to adjust traffic weights and gradually direct more traffic to a new version.

The lab will also explore challenges in route delegation and role-based access control within the Gateway API and potential extensions to address gaps in traffic shaping, access control, and debugging rollouts.