Before You Migrate: Five Surprising Ingress-NGINX Behaviors You Need to Know
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Ingress-NGINX is being retired by Kubernetes in March 2026. Before migrating to Gateway API, there are five non-obvious behaviors to understand: (1) regex path matches are prefix-based and case-insensitive by default; (2) the use-regex annotation applies to all paths for a given host across all Ingresses, not just the annotated one; (3) the rewrite-target annotation silently enables regex mode for all paths on that host; (4) requests missing a trailing slash are automatically redirected with a 301 to the path with a trailing slash; (5) Ingress-NGINX normalizes URLs (handling dot segments and duplicate slashes) before matching. Each behavior is demonstrated with examples and corresponding Gateway API equivalents are provided to help preserve or consciously change these behaviors during migration.
Table of contents
1. Regex matches are prefix-based and case insensitive2. The nginx.ingress.kubernetes.io/use-regex applies to all paths of a host across all (Ingress-NGINX) Ingresses3. Rewrite target implies regex4. Requests missing a trailing slash are redirected to the same path with a trailing slash5. Ingress-NGINX normalizes URLsConclusionSort: