Please fill out this form to register for the event.
The Kubernetes community has announced that the community-managed Ingress Controller, ingress-nginx, will be retired in March 2026. After that date, it will no longer receive updates, bug fixes, or security patches—leaving many teams uncertain about what this means for their production environments.
In this webinar, we’ll clear up the confusion around ingress-nginx retirement and explain why F5 NGINX Ingress Controller remains a stable, open, and actively developed option for Kubernetes ingress—today and for the long term.
We’ll walk through what’s changing and how teams can confidently plan their ingress strategy without disruption.
What the ingress-nginx retirement really means and how it impacts Kubernetes clusters running in production today
Why F5 NGINX Ingress Controller is built for longevity, with a fully open-source Apache 2.0 license, an active public roadmap, and a thriving contributor community
How easy it is to migrate, using the same NGINX engine you already know, with familiar annotations and clear migration guidance
How F5 is future-proofing ingress, with a clear evolution path toward Gateway API through NGINX Gateway Fabric—and optional enterprise support when you need it
When and why to use the enterprise version, including NGINX Plus for high availability, advanced observability, authentication and authorization, and commercial support

