ingress-nginx Retired in 2026: Key Pitfalls Teams Face When Migrating to HAProxy
The ingress-nginx project was officially retired in March 2026, ending all releases and security patches despite being used in roughly half of all Kubernetes clusters. Installations of the retired project proceed without any warnings, meaning automated pipelines can continue deploying it silently. A hands-on migration test revealed that switching to HAProxy Kubernetes Ingress Controller is not simply an annotation-mapping exercise — subtle but serious issues emerge around IP address forwarding and protocol headers. Each network hop rewrites the source address, causing the original client IP to be buried under intermediate addresses, while X-Forwarded-Proto is incorrectly set to HTTP even for HTTPS connections, potentially breaking redirects and secure cookies. An additional practical hazard was found in Cloudflare IP list generation, where a missing newline between IPv4 and IPv6 ranges causes HAProxy to reject its own configuration at load time.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.




Discussion (0)
Log in to join the discussion and vote.
Log in