Ingress-NGINX is being discontinued: Traefik, Gateway API, Service Mesh, or API Gateway?
The Ingress-NGINX project will be officially discontinued in March 2026. Until then, only "best-effort" maintenance will be performed – after that, there will be no more releases, bug fixes, or security updates. What decisions do platform teams need to make now?

Table of Contents
The Ingress-NGINX project will be officially discontinued in March 2026. Until then, only “best-effort” maintenance will be performed – after that, there will be no more releases, bug fixes, or security updates. Existing deployments are expected to continue to function, but without maintenance or security guarantees. For many companies, this is not a minor technical issue, but a strategic risk:
An unpatched, internet-exposed edge component quickly becomes a compliance and operational problem.
Why “letting it continue to run” is not an option!
Even if a system appears stable in the short term:
As soon as security vulnerabilities occur, upstream patches will be missing after March 2026. This has typical consequential effects:
What we recommend by March 2026 at the latest
K8S Cluster with Ingress-NGINX
Extended support windows with SUSE
With a SUSE Enterprise Support Subscription, there is the possibility for RKE2/Rancher setups to rely on extended support (e.g. Rancher Prime LTS). This can give you additional time because security and maintenance issues are covered longer within the SUSE support window (until the end of 2027) – and migrations therefore fit better into planned change and release cycles.
Nevertheless, it remains important:
This is not a “we can ignore it” topic, but a buffer for environments with tight change windows.
The strategic direction remains clear:
Replacement of Ingress-NGINX and modernization of the Ingress/Gateway architecture – but in a controlled manner and with more planning flexibility as well as a strong manufacturer partner – SUSE – and FULLSTACKS as a partner who takes responsibility for your project.
Platform and architecture variants
Ingress/Gateway is rarely “one size fits all.”
Therefore, we derive the decision along your platform and architecture standards:
Recommended Immediate Checks: In 3 Steps to a Resilient Decision
1. INVENTORY
2. DEFINE MIGRATION PATH
3. TECHNICAL PREPARATION
Our offer:
Clarity, predictability and a migration without failure
If you operate Ingress-NGINX productively or need to make a strategic decision in the short term, we would be happy to support you with:







