Since March 24, 2026, Ingress-NGINX has received no new releases, bug fixes, or security patches. Existing installations continue to work, but operational risk increases over time.
A migration should not be treated as a simple replacement of individual YAML resources. Annotations, TLS, authentication, rewrites, network behavior, and controller-specific edge cases must be reviewed systematically.
The discontinuation and end of further releases, bug fixes, and security updates are documented in the Kubernetes v1.36 Release Notes.
How I support this assessment
As part of the “Ingress-NGINX to Gateway API” consulting service, I analyze the relevant configuration primarily through your Git repositories. The result is a structured assessment of migration risks and a clear, technically grounded migration path. Subsequent implementation is not part of the analysis and is not marketed as a standalone standard product.
Would you like to assess your existing Ingress configuration and develop a reliable migration path?