Menu

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 API (2026)

DEV Community: kubernetes·Rabin Adhikari·4 days ago
#w2pAIqvc
#devtokubernetes#devto#dev#ingress#gateway
Reading 0:00
15s threshold

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

TL;DR

The community Ingress NGINX controller ( kubernetes/ingress-nginx ) is retired. Kubernetes announced it on 11 November 2025, shipped the final releases on 19 March 2026, and archived the repository on 24 March 2026. There will be no further releases, bugfixes, or security patches — ever.

This is no longer theoretical: on 5 November 2026 the Kubernetes Security Response Committee published CVE-2026-116472 against ingress-nginx and stated plainly, "Kubernetes will not be issuing a fix for this CVE." Every future CVE gets the same answer.

The Ingress API itself is not deprecated — it is GA and frozen. Only this one controller is dead. F5's separate NGINX Ingress Controller is also unaffected. What you are replacing is the controller, and Gateway API is the replacement Kubernetes recommends.

The migration risk is not the YAML conversion — it is the annotations.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.