FR
live
tag

#gateway-api

ingress-nginx gets a CVE Kubernetes will not fix

On November 5, 2026, the Kubernetes Security Response Committee published CVE-2026-116472, a flaw that lets any user allowed to create an Ingress take down all ingress-nginx traffic through the mirror-target annotation, with no upstream fix because the project’s maintenance ended in March 2026. If your cluster still runs ingress-nginx, plan the move to a maintained controller and tighten your admission rules now.

Kubernetes Gateway API 1.7 promotes HTTPRoute retries to the Standard channel

On October 29, 2026, Kubernetes Gateway API shipped version 1.7.0: HTTPRoute retry configuration graduated to the Standard channel while distributed tracing, pre-routing filters, and session persistence landed as experimental. Teams exposing traffic across multiple gateway implementations should revisit their retry annotations and telemetry policy before upgrading.

Ingress-nginx is end of life: migrate to Gateway API before November 2026

On November 12, 2025, Kubernetes announced the retirement of ingress-nginx; upstream maintenance stopped in March 2026 and the last patch bridge, Microsoft’s for AKS, expires in November 2026. Every annotation in your fleet now has to become a Gateway API route — or remain an unpatched vulnerability.

ingress-nginx is retiring in March 2026: here’s your Gateway API migration plan

The ingress-nginx project ends all maintenance in March 2026. The GitHub repository has been archived since March 24, no further security patches will be published, and CVE-2025-1974 demonstrated the architectural risks of a controller built on arbitrary annotations. Gateway API is the mandatory migration target, and it’s ready.

Type at least two characters.

↑ ↓ navigate ↵ open esc dismiss