Kubernetes Ingress Nginx is retiring
kubernetes.dev
Kubernetes Ingress Nginx is retiring
1–10 of 178 posts
Re: Kubernetes Ingress Nginx is retiring
#2RIP, end of an era. Thank you everyone who worked on this, it was an extraordinarily useful and reliable project.
Re: Kubernetes Ingress Nginx is retiring
#3It wasn't the most loved part of k8s, to say the least.
Re: Kubernetes Ingress Nginx is retiring
#4Does 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.
Re: Kubernetes Ingress Nginx is retiring
#5What's the security back-story here?
Re: Kubernetes Ingress Nginx is retiring
#6Does 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.
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.
Re: Kubernetes Ingress Nginx is retiring
#7Reading 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?
Re: Kubernetes Ingress Nginx is retiring
#8Why would you kill a thing that works so well, is so flexible, and does not have an equal yet?
I do not understand.
Re: Kubernetes Ingress Nginx is retiring
#9Ingress 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.
Re: Kubernetes Ingress Nginx is retiring
#10Why would you kill a thing that works so well, is so flexible, and does not have an equal yet? I do not understand.
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.