Replace legacy Ingress with modern, production-ready traffic management using NGINX Gateway Fabric.
Kubernetes Ingress is on its way out. With NGINX Ingress reaching End-of-Life and the IngressNightmare CVE exposing critical vulnerabilities in legacy approaches, organizations are actively migrating to the Kubernetes Gateway API — a more expressive, extensible, and secure model for managing cluster traffic. This course gives you the hands-on skills to lead that migration. You'll start by understanding exactly why Ingress is being deprecated, how Gateway API's role-oriented architecture separates responsibilities across infrastructure providers, cluster operators, and application developers, and how to deploy your first Gateway using NGINX Gateway Fabric. From there, you'll work through the core Gateway API resources — GatewayClass, Gateway, and HTTPRoute — before moving into advanced traffic management: cross-namespace routing, weight-based traffic splitting for canary deployments, header-based routing for A/B testing, and request and response filters for in-flight traffic manipulation. The course then covers TLS termination, HTTP-to-HTTPS redirect enforcement, and cross-namespace security using ReferenceGrant. The final module focuses on production observability — interpreting Gateway API status conditions, diagnosing common failure scenarios with kubectl, and applying production migration blueprints for safe DNS cutover from legacy Ingress. Who this is for: Kubernetes engineers, platform architects, DevOps engineers, and cloud-native developers responsible for managing cluster networking or migrating away from legacy NGINX Ingress controllers.















