Ingress-nginx, a widely used ingress controller for Kubernetes, is set to be archived at the beginning of 2026, meaning it will no longer receive updates or support. This announcement, made during KubeCon, has significant implications for the 50% of Kubernetes users relying on it. Organizations now face a critical decision: either continue using an unsupported ingress controller or migrate to a supported alternative. The Kubernetes community is moving towards the Gateway API as the preferred standard for traffic management, presenting two main paths for migration. One option is to switch to Cilium Ingress, a compatible replacement that runs on Cilium’s eBPF-powered datapath. This allows for quick adaptation with minimal changes to existing configurations. However, teams should be aware that certain NGINX-specific features won't translate directly, necessitating a validation phase. The second option is to adopt Cilium’s Gateway API implementation. This upgrade provides advanced traffic management capabilities, such as header-based routing and traffic splitting, which are not possible with ingress-nginx. Cilium enhances the Gateway API with better performance and security features. Migrating to this implementation involves defining GatewayClass and Gateway resources, translating existing Ingress rules into HTTPRoute objects, and testing new functionalities. For those managing numerous Ingress resources, the ingress2gateway tool can automate much of this conversion, streamlining the transition.