The Kubernetes ecosystem is evolving, and one of its most iconic components is coming to an end: Ingress NGINX will be retired in March 2026, according to the official announcement from SIG Network and the Security Response Committee. From that date onward, there will be no more updates, security patches, or new features, leaving organizations with the need to migrate to modern and sustainable solutions.
In this session, you will learn:

Why NGINX Ingress is being deprecated:
- Maintenance challenges, technical debt, and security risks.
- What Kubernetes Gateway API is and why it’s considered the official replacement.
- Key differences between the Ingress model and Gateway API: security, scalability, and extensibility.
- Migration plan: how to move from NGINX Ingress to Gateway API without disrupting your applications.

If your infrastructure depends on NGINX Ingress, now is the time to prepare the transition to a more robust architecture aligned with the future of Kubernetes.