Migrating Off Ingress NGINX Ahead of Its Retirement

Wed, 08 Jul 2026 09:00:00 +0000

Ingress NGINX is being retired. Best-effort support until March 2026, then nothing. Need to migrate everything before then.

Structured approach:

Inventory - every cluster, every Ingress resource, every controller config and Helm release.
Assess options - Gateway API, Azure AppGW Ingress Controller, Traefik, Kong, HAProxy, NGINX Gateway Fabric, Blixt.
Select based on maintainability, security, performance, Azure integration, roadmap stability - not just popularity.
Migrate across all clusters.

Upstream retirements are a forcing function to revisit if the original choice is still right. Instead of a like-for-like replacement, this was a real opportunity to evaluate the Gateway API ecosystem that’s matured a lot since we first picked ingress-nginx.

Gateway-Api on GeekyRyan

Migrating Off Ingress NGINX Ahead of Its Retirement