Kubernetes SIG Network ingress-nginx controller retirement by March 2026

The Kubernetes SIG Network ingress-nginx controller, a widely used component for managing external access to services within Kubernetes clusters, is being retired by March 2026. This means its official support, security updates, and new feature development will cease. Organizations currently using this controller must plan to migrate to an alternative solution before the deadline.

This retirement matters because the ingress-nginx controller is a critical piece of cloud-native infrastructure for many companies. Its discontinuation creates an operational security risk for those who do not migrate, as unpatched software can be vulnerable to exploits. It also impacts future feature development and compatibility within their Kubernetes environments.

The mechanism involves organizations identifying their reliance on the ingress-nginx controller and then selecting and implementing a replacement. This migration typically requires reconfiguring their Kubernetes ingress resources, testing the new controller, and updating their deployment pipelines. The process can be complex, depending on the scale and configuration of their existing infrastructure.

This move primarily affects enterprises heavily invested in cloud-native infrastructure and Kubernetes. Companies like Red Hat (IBM), VMware (VMW), and other cloud providers or software vendors offering Kubernetes solutions may see increased demand for their alternative ingress controllers or migration services. Organizations using the retired controller will incur costs and allocate engineering resources for the migration.