CNCF On-Demand: Ingress-Nginx Is Retiring, NGINX Is Not

Why It Matters

Enterprises relying on Kubernetes ingress must reassess support and roadmap, ensuring continuity and leveraging newer Gateway API capabilities for scalability and security.

Key Takeaways

• ingress-nginx project will be archived by CNCF.
• NGINX Ingress Controller continues active development.
• NGINX Gateway Fabric supports Gateway API.
• Evaluate Ingress vs Gateway API for future deployments.
• Migration paths provided for existing ingress-nginx users.

Pulse Analysis

Kubernetes has long depended on the Ingress resource to expose services, and the ingress‑nginx controller became the de‑facto standard for many clusters. In early 2024, the Cloud Native Computing Foundation announced that the ingress‑nginx project would be retired, sparking headlines that suggested the entire NGINX stack was disappearing. The announcement, however, only affects the community‑maintained controller repository; the underlying NGINX engine and its commercial derivatives remain fully supported. Understanding this distinction is essential for teams that have built production workloads around NGINX‑based ingress.

For organizations currently using ingress‑nginx, the retirement means the codebase will no longer receive new features or security patches, though existing versions will stay functional. The recommended path is to transition to the NGINX Ingress Controller, which offers a compatible API surface plus enterprise‑grade enhancements, or to adopt NGINX Gateway Fabric, which implements the emerging Gateway API with richer traffic‑management primitives. Both projects are backed by NGINX, Inc. and receive regular updates, providing a clear migration roadmap and reducing operational risk.

Choosing between the classic Ingress controller and the Gateway‑centric Fabric hinges on workload complexity and future‑proofing goals. Teams that need advanced load‑balancing, multi‑tenant isolation, or progressive rollout capabilities should evaluate the Gateway API’s extensibility, while simpler use‑cases may stay on the Ingress controller with minimal code changes. Early adoption of the Gateway API also aligns with the broader CNCF roadmap, positioning enterprises to benefit from upcoming ecosystem tools and standards. In short, the retirement is a catalyst for modernizing Kubernetes edge traffic handling rather than a disruption.

Original Description

When the Kubernetes community announced the retirement of ingress-nginx, confusion followed. Many thought NGINX or even the Ingress API was going away. In reality, NGINX-based solutions like NGINX Ingress Controller and NGINX Gateway Fabric remain active and thriving. This talk clarifies the naming confusion, what the retirement really means, and how to evaluate your Ingress and Gateway API options moving forward.