Half of Kubernetes Clusters Are About to Lose Security Updates

Roughly 50% of cloud native environments use Ingress NGINX. In March 2026, it stops receiving security patches. I sat down with Kat Cosgrove (Kubernetes Steering Committee) and Tabitha Sable (Kubernetes Security Response Committee, SIG Security co-chair) to understand why the project is being retired, what it means for users, and how to check if you're affected. Key takeaways: End of March 2026: no more releases, no more security patches No drop-in replacement exists CNCF recommends migrating to Gateway API Simple check: does your cluster have a namespace called "ingress-nginx"? 🔗 Resources: Official announcement: https://kubernetes.io/blog/2025/11/11... Ingress NGINX repo: https://github.com/kubernetes/ingress... Gateway API docs: https://gateway-api.sigs.k8s.io/ ⏱️ Timestamps: 0:00 Intro 0:30 What is Ingress NGINX? 3:59 How widely used is it? 5:05 What does retirement mean? 6:32 Migration options 7:46 Why is it being retired? 10:40 Security implications 12:00 How to check if you're using it 15:00 Final advice The Landscape is a podcast about the CNCF landscape and beyond, featuring project maintainers, contributors, and end-users. This episode was sponsored by Rootly – a leading AI-powered on-call and incident response. Trusted by leading companies like NVIDIA, Squarespace, Canva, Figma, and more. #Kubernetes #CNCF #IngressNGINX #CloudNative #DevOps #GatewayAPI #OpenSource