Cutting Through the Kubernetes Confusion: NGINX Ingress, Gateway Fabric, and What's Next
summary
Clarifies that the community NGINX Ingress controller is retired while F5’s actively developed NGINX Ingress Controller remains maintained and is adding missing annotations; community NGINX once ran on roughly 50% of clusters. Explains that NGINX Gateway Fabric implements the evolving Gateway API (top-five conformant), that a migration tool maps community annotations to the controller, and that the Gateway API Inference Extension routes LLMs via an IngressPool using metrics like KV cache and queue depth; roadmap adds external auth, mTLS and more.
AI-written summary · about
chapters (11)
- 0:00Kubernetes and speakers
- 0:22Ingress vs Gateway Fabric
- 1:47Gateway API evolution
- 3:10F5’s Gateway API
- 3:32Ingress Engine X explained
- 4:58Migrating to F5 Ingress
- 5:38AI with Gateway API
- 6:43Observability with NGINX JS
- 7:04Open source roadmap
- 7:25Future of Ingress & Gateway
- 9:14Community resources
related talks
28mApplication delivery on k8s - the past, present and future
37mJourney Through Kubernetes Ingress: Past, Present, and Beyond
28mMaking the Leap: What Gateway API Needs To Support Ingress-NGINX Users
49mAdvanced Ingress for Your Kubernetes Apps
01mWhat is
35mUnderstanding the Future of Ingress-nginx
15mSimplify Kubernetes Connectivity
35mThe Next Steps for Ingress-NGINX and the Ingate Project