Why action is needed

Ingress-NGINX has not received new releases, bug fixes, or security patches since March 24, 2026. Existing installations continue to work, but operational risk increases over time.

Typical starting point

Your Ingress configuration contains accumulated rules, annotations, or edge cases. Before migrating to the Gateway API, risks, dependencies, and a robust migration path should be clarified systematically.

Configuration areas analyzed

Routing, hosts, paths, and rewrites.
TLS, authentication, and additional annotations or policy requirements.
Controller selection, network behavior, and relevant edge cases.
Migration risks, parallel operation, and appropriate validation steps.

Outcome and deliverables

You receive a structured assessment of migration risks and a clear technical migration path. The scope, configurations reviewed, and deliverables are clearly defined and agreed upon in the proposal before work begins.

Process

After a brief initial consultation, we align on the starting point, objective, and scope. We then review the repository-based analysis together and turn it into actionable next steps.

Requirements and repository-based collaboration

The analysis is primarily based on the relevant Git repositories and available technical documentation. Direct access to production systems is not part of the standard review. If information about the live state is required, the customer team provides selected exports, screenshots, or mutually agreed outputs.

The specific scope is determined based on your environment and agreed upon in writing in the proposal.

Distinction between analysis and full migration

The migration analysis assesses the existing setup and describes the migration path. Subsequent implementation is not part of the analysis and is not offered as a separate standard product. Not every existing feature can be transferred to the Gateway API without adjustments.

What is not included

Direct access to production systems or ongoing operational responsibility.
A blanket full migration or implementation of all measures.
24/7 support, managed services, or unlimited analysis of additional configurations.

Frequently asked questions

Is the entire migration implemented?

The standard service is a migration analysis. Subsequent implementation can be agreed on individually, but is not offered as a separate standard product.

Will every existing Ingress rule continue to work unchanged?

No. Annotations and controller-specific edge cases are assessed specifically; necessary adjustments may result.

How is the scope determined?