Skip to main content
DevOps 1 min read 369 views

Ingress NGINX Moving to Best-Effort Maintenance, Retiring March 2026

Kubernetes project reduces support level, recommending Gateway API for new deployments going forward.

TD

TechDrop Editorial

Share:

The Kubernetes project announced on February 1 that Ingress NGINX will move to best-effort maintenance mode, with the Gateway API recommended for new deployments starting March 2026.

Transition Plan

Ingress NGINX will receive critical security fixes but no new features. The project recommends new deployments use the Gateway API, which provides more flexibility and better multi-tenancy support.

Gateway API Advantages

Gateway API offers role-oriented design, allowing platform teams to manage infrastructure while application teams configure routes. It supports advanced routing, better observability, and extensibility through custom resources.

Migration Path

Existing Ingress NGINX users can continue using it, but should plan migration to Gateway API implementations. Major ingress controllers including NGINX Gateway Fabric, Istio, and Envoy Gateway support the new API.

Industry Impact

The shift reflects Kubernetes' evolution from simple ingress to sophisticated traffic management. Gateway API represents lessons learned from years of Ingress usage, addressing limitations that became apparent at scale.

Related Articles

DevOps 2 min read

Docker Engine 29.3 Ships with Native gRPC Support and BuildKit v0.28

Docker Engine 29.3.0 introduces native gRPC support on listening sockets, BuildKit v0.28.0, and a new bind-create-src option for flexible volume mounting. The release lowers the minimum API version to v1.40 for broader backward compatibility and fixes DNS configuration corruption during daemon reloads.