Migrating from ingress-nginx and the Ingress API to the Kubernetes Gateway API and agentgateway
This workshop is intended for DevOps professionals faced with the challenge of migrating from the ingress-nginx controller, one of the early Kubernetes ingress controllers.
The recent announcement of the retirement of the ingress-nginx project presents an opportunity to migrate to the latest standards for Kubernetes service networking.
In this workshop, we will walk you through concrete scenarios that demonstrate how to migrate Ingress configurations to agentgateway, a modern Gateway implementation that is fully conformant with the Kubernetes Gateway API.
You will use the `ingress2gateway` migration tool to translate ingress resources with ingress-nginx specific annotations.
The tool goes beyond basic ingress scenarios that generate Kubernetes Gateway API resources: It also generates agentgateway-specific Custom Resource Definitions that capture advanced network configurations such as TLS, rate limiting, and canary deployments.
This workshop is intended for DevOps professionals faced with the challenge of migrating from the ingress-nginx controller, one of the early Kubernetes ingress controllers.
The recent announcement of the retirement of the ingress-nginx project presents an opportunity to migrate to the latest standards for Kubernetes service networking.
In this workshop, we will walk you through concrete scenarios that demonstrate how to migrate Ingress configurations to agentgateway, a modern Gateway implementation that is fully conformant with the Kubernetes Gateway API.
You will use the `ingress2gateway` migration tool to translate ingress resources with ingress-nginx specific annotations.
The tool goes beyond basic ingress scenarios that generate Kubernetes Gateway API resources: It also generates agentgateway-specific Custom Resource Definitions that capture advanced network configurations such as TLS, rate limiting, and canary deployments.
