Don't Panic: A Low-Risk Strategy for Ingress NGINX Retirement
The Ingress NGINX project is winding down. For many organizations, this means planning a migration for critical infrastructure. While the HAProxy Kubernetes Ingress Controller is the natural successor for these workloads, a "rip and replace" strategy isn’t always viable. You might have complex configurations, customized annotations, or deployment freezes that make a sudden switch risky. There's a lower-risk path: Place HAProxy in front of your existing Ingress NGINX deployment.