Making the Leap: What Gateway API Needs To Support Ingress-NGINX Users
Talkat KubeCon + CloudNativeCon Europe 2025 · on Wednesday, 2025-04-02· at 17:45· Level 0 | ICC Capital Hall | Room I·
summary
Migration plan targets the 118 annotation-driven features of Ingress-NGINX: only 35% implemented in Gateway API today, ~55% marked "supported soon", and many categories with no plan. Strategy adds two temporary API slots, three releases across 2025–26 to cover priority categories (roughly a dozen category-level entries), and a new ingress-focused implementation called ingate plus tooling—gateway-cuddle (v0.1) already shows resource graphs and points-to analysis—to ease migration while ingress-nginx moves to maintenance and conformance-based stability.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 0:52Project goals and strategy
- 3:28Rationale for the migration
- 6:42Analyzing feature parity
- 9:40Identifying critical gaps
- 11:12Unlocking future potential
- 13:13Addressing usability hurdles
- 17:14Improving user experience
- 18:55Closing the migration gap
- 21:17Implementation timeline
- 25:16Call to action and conclusion
related talks
33mExiting Ingress With the Gateway API
35mIngress-Nginx: The Day After
10mCutting Through the Kubernetes Confusion: NGINX Ingress, Gateway Fabric, and What's Next
35mUnderstanding the Future of Ingress-nginx
24mLeveraging Gateway API for Kubernetes Native API Management
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
28mApplication delivery on k8s - the past, present and future
28mBeyond Kubernetes Ingress (with Gateway API)