I Tested 7 So You Only Need 1: Your First Gateway API Migration in 5 Minutes
summary
PoC tests 7 implementations across 17 scenarios and shows a reproducible, minimal path: use ingress2gateway to convert Ingress YAML, apply Gateway API resources, and restore the same public IP so continuous curl goes from working to broken to recovered within a 5‑minute live cycle. Demo works but the converter requires verification and occasional redesign; rewrite/path behavior can fail and zero‑downtime swap is only supported by Istio and K Gateway.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:47Migrate from Ingress to Gateway API
- 7:48Gateway API implementations
- 11:19Ingress to Gateway API migration demo
- 17:59Recap and call to action
- 20:48Q&A
related talks
30mIs Zero-Downtime Migration Possible? Moving From Ingress & Sidecars To Gateway API
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
28mMaking the Leap: What Gateway API Needs To Support Ingress-NGINX Users
32mTaking Back Control of Your APIs with Gateway API
24mA Hands-On Introduction to the Kubernetes Gateway API with Apache APISIX
24mLeveraging Gateway API for Kubernetes Native API Management
28mA Look at Istio's Journey with the Gateway API
28mApplication delivery on k8s - the past, present and future