"A lot of organizations aren't going to shift away from it -- even though it's got known vulnerabilities that are being exploited -- for the same reason they didn't shut it off two or three years ago, which is that it worked two or three years ago, and it still works now. Replacing it with another technology means all your APIs need to communicate correctly. The CRDs there need to be reliable.

"[Some users] could be told today that something is incredibly insecure, it's likely to be compromised, and ignore that, and say, 'But it still works at the end of the day.' That's a serious problem." ~ Nigel Douglas, head of developer relations at #CNCF member company Cloudsmith and a former contributor to the Falco CNCF project, in an interview this week about the retirement of the #IngressNginx project and its potential impact on users who might remain unaware that the project is no longer receiving community support, including security patches, following its final release March 13.

My writeup on the discussions during #KubeConEU this week: https://www.techtarget.com/searchitoperations/news/366640683/CNCF-Ingress-Nginx-retirement-could-leave-some-users-at-risk

Kubernetes networking is evolving 🌐 with the rise of the Gateway API, offering more flexible and extensible traffic management.

CrowdSec continues to support Ingress-NGINX during its final lifecycle, while helping users migrate to modern ingress controllers like Traefik and HAProxy, or Gateway API integrations, for future-proof security 🔒.

Read our latest article for details: https://www.crowdsec.net/blog/crowdsec-support-kubernetes-ingress-nginx

#Kubernetes #IngressNGINX #GatewayAPI

Nueva entrada en la web: "Guía Práctica: Sustituyendo Ingress-NGINX por Envoy Gateway (Paso a Paso)" #IngressNginx #EnvoyGateway #Nginx

https://www.ochobitshacenunbyte.com/2026/02/19/guia-practica-sustituyendo-ingress-nginx-por-envoy-gateway-paso-a-paso/

Ingress NGINX Retirement

- Best-effort maintenance will continue until March 2026.
- Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered.
- Existing deployments of Ingress NGINX will not be broken.
- Existing project artifacts such as Helm charts and container images will remain available.

https://github.com/kubernetes/ingress-nginx

#kubernetes #IngressNGINX

Kubernetes kończy z Ingress NGINX – czas na migrację i nowe wyzwania

Czy Twój klaster ma właśnie tykającą bombę z opóźnionym zapłonem? Jeśli korzystasz z Ingress NGINX, odpowiedź może brzmieć: tak.

Czytaj dalej:
https://pressmind.org/kubernetes-konczy-z-ingress-nginx-czas-na-migracje-i-nowe-wyzwania/

#PressMindLabs #gatewayapi #ingressnginx #istio #kubecon #kubernetes

Nova verzija Kubernetesa fokusira se na stabilnost, sigurnost i kraj za Ingress Nginx.

#Cyber #Magazin #Vijesti #Kubernets #IngressNginx

Pročitaj više: https://cyber.ba/kubernetes-1-35-donosi-stabilnije-upravljanje-i-kraj-za-ingress-nginx/

Sinceramente, no sé a qué viene tanto drama entre la comunidad de Kubernetes con la descontinuación del proyecto Ingress Nginx cuando existen montones de implementaciones de Ingress Controller además de Nginx.

¡Oh! ¡Ingress ha muerto! ¡Larga vida a Gateway API!.

Menudo alarmismo.

#kubernetes #k8s #ingressnginx

Shit hit the fan a couple of days ago, when the #ingressnginx team announced that they're retiring the project. Ingress NGINX has been my #Kubernetes #ingress controller of choice since forever, and this came a quite a shock.

Right now, it looks like the #Traefik ingress controller is the most viable choice for an easy plug-in replacement. I'm giving it a test run on my home cluster, which is running all sorts of weird things that make up a good technical test. #Jellyfin seems like it's working well with WebSockets and all, and raw TCP to Mosquitto is working well too.

Obviously this is rather low traffic, but it looks like this could be a future replacement on the #Midgaard cluster running https://mstdn.dk - no matter what, staying on a burning ingress controller is not an option.

https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/

#ingressnginxgate

#IngressNginx will be retiring in March 2026 😰

We knew it was coming! One year ago we learned that it was in maintenance mode.

KubeCon NA 24 (November) - Securing the Future of Ingress-Nginx: https://www.youtube.com/watch?v=KLwsV6_DntA

Still surprising:
* It will be retiring in only 4 months
* There won't be a successor, instead #ingate will be retiring, too 🤯

Now is the time to choose a new ingress controller and make migrations plans.

Which one will become the new de-facto standard?