Kubernetes Ingress Nginx is retiring
14 comments
·November 13, 2025SlavikCA
null
stackskipton
It doesn't but Kubernetes team was kind of like "Hey, while you are switching, maybe switch away from Ingress API?"
benatkin
This sort of centralized deprecating/archiving of subprojects is toxic.
It should be allowed to take on new maintainers without this sort of announcement. It reminds me of when GitHub shut down the Atom text editor.
sleazebreeze
RIP, end of an era. Thank you everyone who worked on this, it was an extraordinarily useful and reliable project.
andix
Does anyone know good resources on how to migrate and which gateway controllers are suitable replacements?
Ingresses with custom nginx attributes might be tricky to migrate.
seabombs
I've been using Envoy Gateway in my homelab and have found it to be good for my modest needs (single node k3s cluster running on an old PC). I needed to configure the underlying EnvoyProxy so that it would listen on specific IPs provided by MetalLB, and their docs were good enough to find my way through that.
imcritic
But envoy configs are unreadable abominations, why would you choose it? How did you even learn how to configure it? It's documentation is so confusing.
all_usernames
What's the security back-story here?
etchalon
Why would you kill a thing that works so well, is so flexible, and does not have an equal yet?
I do not understand.
seneca
There are no maintainers. It was maintained by one engineer for years, he stepped down, and F5 (who bought nginx) don't want to contribute since they have a competitor.
seneca
Ingress nginx was the default ingress for pretty much the entire life of k8s. F5 bought nginx and made nginx ingress, which I've never met a user of.
Sad to see such a core component die, but I guess now everyone has to migrate to gateways.
stackedinserter
It wasn't the most loved part of k8s, to say the least.
yahoozoo
Great, another deprecation to address in my EKS clusters :(
Reading few blogs and forums about it today - people talking about switching to Gateway API (from "legacy" Ingress).
And I do not understand it:
1. Ingress still works, it's not deprecated.
2. There a lot of controllers, which supports both: Gateway API and Ingress (for example Traefik)
So, how Ingress Nginx retiring related / affects switch to Gateway API?