Kubernetes Gateway API 2026: v1.5, v1.6, and Saying Goodbye to Ingress-NGINX

The year 2026 marks a turning point for the Kubernetes network: With the retirement of Ingress-NGINX in March and two major Gateway API releases (v1.5 and v1.6), the replacement of classic Ingress is imminent. This article shows what the new versions bring, why the timing is favorable, and how migration succeeds.

Gateway API v1.5: From Experimental to Standard

On February 27, 2026, SIG Network released Gateway API v1.5 – the most extensive release to date. For the first time, the project switched to a release-train model modeled on Kubernetes itself: By the feature-freeze deadline, all completed features are included in the release, without waiting for individual milestones.

Six important features reached the Standard Channel (GA status):

• ListenerSet – Previously, all listeners had to be defined directly in the Gateway object. ListenerSet allows listeners to be defined independently and merged onto a Gateway. This is particularly relevant for multi-tenant scenarios where platform and application teams manage different listeners. More than 64 listeners per Gateway also become possible.
• TLSRoute – Enables route-based TLS forwarding without HTTP awareness, e.g., for database connections or message queues.
• HTTPRoute CORS Filter – native CORS handling directly in the route, without implementation-specific annotations.
• Client Certificate Validation and Certificate Selection – advanced TLS features for Gateway termination.
• **Reference