Ingress NGINX Controller has reached end of life as of March 2026, forcing platform teams to migrate. Four strategies are outlined: switching to another ingress controller (requires rewriting all annotations), adopting a community fork (inherits architectural vulnerabilities), migrating directly to Gateway API (couples urgent security fix with major architectural change), or using a controller that natively supports both Ingress NGINX annotations and Gateway API. The fourth approach, exemplified by Traefik's Ingress NGINX Provider, is presented as the safest path: replace the controller without changing existing manifests, then progressively adopt Gateway API at your own pace. A three-phase migration process is recommended: audit your cluster, perform a zero-downtime controller swap, then modernize incrementally.
Table of contents
Strategy 1: Migrate to Another Ingress ControllerStrategy 2: Adopt a Fork of Ingress NGINXStrategy 3: Migrate Directly to Gateway APIStrategy 4: Use a Controller that Supports Both Ingress NGINX Annotations and Gateway API NativelyA Three-Phase MigrationPhase 1: Assess Your SituationPhase 2: Decommission Ingress NGINX with Zero DowntimePhase 3: Modernize ProgressivelyThe Bigger PictureRelatedSort: