The End of kubernetes/ingress-nginx: Your March 2026 Migration Playbook

In March 2026, the community-maintained kubernetes/ingress-nginx controller will reach End-of-Life (EOL). While your existing clusters will not break overnight and the core Kubernetes Ingress API remains fully supported, the controller's repository will become read-only. This means no new features and, critically, no future CVE patches . Engineering teams must plan their migrations now to avoid compounding security risks and compliance violations. It’s common to leave functioning infrastructure untouched, but running deprecated software in your cluster’s critical path introduces unnecessary risk. With a public and immovable deadline, engineering teams have a clear window to plan a structured migration rather than reacting hastily to a future vulnerability. What’s Actually Happening with ingress-nginx March 2026 Retirement Let’s be crystal clear on terminology, because confusion here is costing teams weeks. The Kubernetes Ingress API resource remains GA, feature-frozen, and fully suppor