> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Course Overview > Course guiding adoption of the Gateway API with NGINX Fabric Gateway, covering NGINX Ingress retirement, architecture, advanced routing, security, and production migration This course provides a practical, in-depth guide to how NGINX implements the Gateway API. You'll get technical explanations, architectural diagrams, and hands-on guidance to help you adopt the Gateway API in real-world Kubernetes environments. What we'll cover (in order): 1. NGINX Ingress retirement: what happened, why it matters, and how to plan for it. 2. The Gateway API as the new standard and the motivation behind it. 3. NGINX's approach and architecture for implementing the Gateway API. 4. A deep dive into Gateway API resources, including advanced and secure routing. 5. Production considerations and migration planning before publishing a Gateway API-based solution. A presentation slide titled "What You Will Learn" showing a horizontal timeline with colorful pin markers and icons. The timeline highlights topics like NGINX Ingress retirement, Gateway API as the new standard, NGINX Fabric Gateway, advanced/secure routing, and migration to a production-ready Gateway API. Course modules at a glance: | Module | Focus | Outcome | | - | - | - | | 1 — NGINX Ingress retirement | Why it was deprecated, implications for clusters | Plan a safe transition strategy | | 2 — Gateway API fundamentals | Core concepts, resources, and motivations | Understand the new standard | | 3 — NGINX Fabric Gateway architecture | How NGINX implements Gateway API | Map features to architecture and components | | 4 — Advanced routing & security | Layer 7 routing, TLS termination, authentication, and policies | Implement secure, production-ready routing | | 5 — Production readiness & migration | CVE mitigation, testing, rollout, and rollback strategies | Execute a migration with reduced risk | Recommended background: intermediate to advanced Kubernetes knowledge, a grasp of networking concepts (L4/L7 routing), and basic security fundamentals (TLS, auth, access control). You don't need to be an expert — this course revisits important concepts as they apply to Gateway API and NGINX. Prerequisites * Intermediate to advanced Kubernetes experience. * Familiarity with networking concepts: routing, L4/L7 behavior. * Basic security awareness: TLS, authentication, and access control. We will walk through the full lifecycle of adopting a new API: planning adoption, mitigating CVEs and security issues, and managing the end of community support. These are critical considerations for production environments. A slide titled "NGINX Deprecation" showing three numbered steps: 01 Adoption of a new API, 02 CVEs mitigation, and 03 End of community support, each with a corresponding colored icon. The three steps are displayed on a horizontal colored progress bar. Important: community support ending does not immediately break existing deployments, but it changes your maintenance and security posture. This course explains how to assess risk, mitigate CVEs, and plan a safe migration to Gateway API-based solutions. Links and references * Gateway API: [https://gateway-api.sigs.k8s.io/](https://gateway-api.sigs.k8s.io/) * Kubernetes docs: [https://kubernetes.io/docs/](https://kubernetes.io/docs/) * NGINX documentation: [https://www.nginx.com/resources/](https://www.nginx.com/resources/) That's it for this overview — proceed to the next module to start with the NGINX Ingress retirement timeline and migration planning. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.