|
- Ingress NGINX Retirement: What You Need to Know | Kubernetes . . .
To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX Best-effort maintenance will continue until March 2026
- Kubernetes Community Retires Popular Ingress NGINX Controller
The Kubernetes SIG Network and the Security Response Committee has announced the retirement of Ingress NGINX, one of the most widely deployed ingress controllers in the ecosystem Best-effort
- The End of an Era: NGINX Ingress is Retiring. Whats next for . . .
In a seismic shift for the cloud-native community, the Kubernetes project maintainers group has announced it is officially retiring the ubiquitous Ingress NGINX controller
- Ingress NGINX Is Retiring. . . - Julian Foster
On November 11, 2025, Kubernetes SIG Network and the Security Response Committee announced the retirement of the community Ingress NGINX controller, with only best-effort maintenance until March 2026 and no security fixes thereafter
- Users scramble as critical open source project left to die
Opinion There were lots of announcements about Kubernetes at KubeCon North America in Atlanta I should know, I was there from beginning to end But the biggest Kubernetes story of all didn't get much attention Kubernetes is retiring its popular Ingress NGINX controller Ingress NGINX goes to that
- Stop the Panic: NGINX is NOT Dead: Understanding the ingress . . .
On November 11, 2025, the Kubernetes SIG Network and Security Response Committee announced the retirement of the ingress-nginx project And predictably, social media and forums are already ablaze with misconceptions about "NGINX dying" or "Kubernetes dropping NGINX support "
- Kubernetes Is Retiring Its Popular Ingress NGINX Controller
During last month's KubeCon North America in Atlanta, Kubernetes maintainers announced the upcoming retirement of Ingress NGINX "Best-effort maintenance will continue until March 2026," noted the Kubernetes SIG Network and the Security Response Committee "Afterward, there will be no further releas
|
|
|