Ingress NGINX Controller for Kubernetes Retires – Where to Go From Here

The Kubernetes ecosystem is facing a significant shift with the scheduled retirement of the Ingress NGINX controller, effective March 2026, which will cease receiving updates, bug fixes, and security patches. This change poses challenges for organizations dependent on it, such as those using Fastly Security services, as they must consider new security and architectural strategies. Short-term solutions include adopting commercial Ingress controllers or using the Chainguard-maintained fork of ingress-nginx, which offers temporary security maintenance without immediate migration efforts. For a long-term approach, organizations can transition to the Kubernetes Gateway API, aligning with industry trends for robust traffic management, or adopt an alternative proxy like HAProxy for a secure, reliable replacement. Fastly is committed to assisting customers through this transition by providing expertise and support in selecting the most suitable path forward.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.