timetobail
My stack

Ingress NGINX (Kubernetes) · Closing down · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Ingress NGINX controller for Kubernetes?

Time to Bail · Boarding pass

FromIngress NGINX controller for Kubernetes
ToYour pick

Yes.

Ingress NGINX was retired in March 2026. It still runs, but gets no security fixes. Plan a replacement.[2]

Bail means: it is ending, or getting much worse, for this group. Leave before the date.

Gate closes
No set date
Check the notice for the date on your plan.
Time left
No set date
Status
Bail

Ingress NGINX is retired: no more security fixes since March 2026

The Kubernetes project retired Ingress NGINX in March 2026. It gets no releases, bug fixes or security fixes. Clusters that run it keep working, so many teams do not know they are exposed.

What to do next

Tick steps as you go. Your progress stays in this browser.

  1. Check if you run it

    Look for the ingress-nginx controller in every cluster. Managed add-ons may use it too.

  2. Pick a replacement

    Kubernetes suggests Gateway API, or another Ingress controller. Test your rules and TLS on it.

  3. Move one app at a time

    Run the new controller next to the old one and move traffic app by app.

Facts we checked

Facts and their sources
RetiredMarch 2026[2]
After retirementNo releases, bug fixes or security fixes of any kind[2]
Do existing installs stop?No. They keep working, and Helm charts and images stay available[1]
The codeGitHub repositories are read-only, kept for reference[1]
How common it isAbout half of cloud native environments, per the Kubernetes Steering Committee[2]
What Kubernetes suggestsGateway API, or another Ingress controller from the Kubernetes docs[1]
Is there a drop-in replacement?No. None of the alternatives is a drop-in replacement[2]
Clusters running Ingress NGINXKeep working but get no security fixes[2]

Sources

Check it yourself. Every fact above links here.

  1. Ingress NGINX Retirement: What You Need to Know Kubernetes · primary · checked Oct 13
  2. Ingress NGINX: Statement from the Kubernetes Steering and Security Response Committees Kubernetes · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Ingress NGINX controller for Kubernetes? Yes. Ingress NGINX was retired in March 2026. It still runs, but gets no security fixes. Plan a replacement.

On our scale this is Bail: it is ending, or getting much worse, for this group. Move your work out now.

The Kubernetes project retired Ingress NGINX in March 2026. It gets no releases, bug fixes or security fixes. Clusters that run it keep working, so many teams do not know they are exposed.

Here are the facts we checked:

  • Retired: March 2026 (Kubernetes)
  • After retirement: No releases, bug fixes or security fixes of any kind (Kubernetes)
  • Do existing installs stop?: No. They keep working, and Helm charts and images stay available (Kubernetes)
  • The code: GitHub repositories are read-only, kept for reference (Kubernetes)
  • How common it is: About half of cloud native environments, per the Kubernetes Steering Committee (Kubernetes)
  • What Kubernetes suggests: Gateway API, or another Ingress controller from the Kubernetes docs (Kubernetes)
  • Is there a drop-in replacement?: No. None of the alternatives is a drop-in replacement (Kubernetes)
  • Clusters running Ingress NGINX: Keep working but get no security fixes (Kubernetes)

This is a full shutdown, not a pause. When the service closes, files and lists you did not save may be gone.

Do not wait for a last reminder email. Those emails are often late, and some never come.

Kubernetes is the main source for this page. Ingress NGINX (Kubernetes) has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Clusters running Ingress NGINX: Keep working but get no security fixes.

Export takes some work. Try it once now, before you need it.

There is no single date for everyone. Your own renewal date is the one that counts.

What to do now

  1. Check if you run it. Look for the ingress-nginx controller in every cluster. Managed add-ons may use it too.
  2. Pick a replacement. Kubernetes suggests Gateway API, or another Ingress controller. Test your rules and TLS on it.
  3. Move one app at a time. Run the new controller next to the old one and move traffic app by app.

A few rules help every move go well:

  • Save what you can first. Pick the new tool after that.
  • Keep every export in two places, like your laptop and a cloud drive.
  • Test the new tool with a small part of your data before you move it all.
  • Tell your users or team once, in one short and clear message.

How to tell your users

Send one short email. Say what changed, where to find you now, and what they need to do. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People leaving Ingress NGINX controller for Kubernetes need a new home. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product