
Ingress NGINX Is Retired and Unpatched: A Working Engineer's Migration Checklist to Gateway API (2026)
Ingress NGINX Is Retired and Unpatched: A Working Engineer's Migration Checklist to Gateway...
Tag archive

Ingress NGINX Is Retired and Unpatched: A Working Engineer's Migration Checklist to Gateway...
Ingress NGINX is in maintenance mode, and the Kubernetes project has been nudging everyone toward...
With Gateway API v1.6 and GA support from AWS, the Gateway API has established itself as the standard for Kubernetes networking in 2026. The article explains TCPRoute, UDPRoute, the three-layer model,
Every OpenShift cluster ships with at least two ways to expose an HTTP service, and since 4.14 there...
Every OpenShift cluster ships with at least two ways to expose an HTTP service, and since 4.14 there...

Introduction If you've been running Kubernetes workloads in production, you've almost...
With Gateway API v1.5 and v1.6 and the retirement of Ingress-NGINX, 2026 is the year of Kubernetes networking modernization. ListenerSet, standard TCP/UDP routing, and the Ingress2Gateway 1.0 migratio
現有 Ingress 要先換 controller,還是改寫成 Gateway API?用 HTTPS 轉址、IP 白名單與長連線的實測例子,比較兩條路線及轉換工具的限制。
A practical review of Gateway API client-certificate validation, listener inheritance, and authorization boundaries.
The June 30 release of Kubernetes Gateway API v1.6 graduates raw L4 TCPRoute and UDPRoute to the Standard channel under v1, deprecates their v1alpha2 counterparts, and moves remaining experimental resources into a separate API group so the boundary between stable and unstable shapes stops being a naming convention.
Introduction: Navigating the Ingress to Gateway API Migration in Kubernetes The Kubernetes...
The Kubernetes SIG Network retired ingress-nginx in March 2026, leaving clusters still on it exposed to unpatched CVEs and stalled feature work. A CNCF post lays out the two migration paths operators are picking between and the tooling to make the move.