timetobail
My stack

Playbook for makers · Shutdown · free while in beta

Bail

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

Ingress NGINX controller for Kubernetes closes: readers save what they can and replace that one function.

No deadline yet. · Public page

Low switching pressure21/100

An estimate from the deadline, cost, discussion and need to move. It is not a product rating.

What goes into it

Confidence: low.

deadline0/30
money14/25
attention0/25
audience0/12
force7/8
  • No deadline. People complain but few move. Treat as weak unless attention is high.
  • The change is forced: it reaches users even if they wait.

  1. 1 Related discussions

    Only threads tied to this event that talk about leaving, moving or prices. Saved, not live. Check the date and read the thread before replying.

    No live threads yet.

  2. 2 What leavers ask

    No common questions yet.

  3. 3 Reply templates

    Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

    Helpful first
    Sorry you have to deal with this. Ingress NGINX controller for Kubernetes closes. Save what you can first:

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.

Know the limits:
- After retirement: No releases, bug fixes or security fixes of any kind.
- Do existing installs stop? No. They keep working, and Helm charts and images stay available.
- Is there a drop-in replacement? No. None of the alternatives is a drop-in replacement.

To replace Ingress NGINX controller for Kubernetes, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]
    Short answer
    Ingress NGINX controller for Kubernetes closes. Save what you can first: check if you run it. Then pick a replacement. Note: After retirement: No releases, bug fixes or security fixes of any kind.
Happy to help if you get stuck with the move.
[Disclosure: I build <your product>.]

  4. 4 Switch-page builder

    Create a draft “Switch from Ingress NGINX controller for Kubernetes” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

    • Add your product name to replace “Your product”.
    Preview

    Switch from Ingress NGINX to Your product

    Ingress NGINX controller for Kubernetes closes. Here is how to save what you can and move to Your product.

    What closes at Ingress NGINX (Kubernetes)

    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.

    • 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.

    What you cannot take with you

    • After retirement: No releases, bug fixes or security fixes of any kind.
    • Do existing installs stop? No. They keep working, and Helm charts and images stay available.
    • Is there a drop-in replacement? No. None of the alternatives is a drop-in replacement.

    What Your product gives you

    Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

    How to move from Ingress NGINX controller for Kubernetes to Your product

    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.
    4. Import into Your product. Say which files you accept and how long an import takes.

    Tell readers to move before their next renewal.

    Questions people ask

    If Your product has a direct answer to one of these, add it here. Keep it short and true.

    How to help new users settle in

    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.

    Sources

  5. 5 Search ideas to validate

    suggested, not measured Phrases people may search when a tool changes like this. We have no search volume data for them.

    • ingress nginx controller for kubernetes
    • ingress nginx (kubernetes) alternative
    • ingress nginx (kubernetes) alternatives
    • ingress nginx (kubernetes) export
    • how to leave ingress nginx (kubernetes)
    • switch from ingress nginx (kubernetes)
    • ingress nginx (kubernetes) shutting down
    • ingress nginx (kubernetes) shutting down 2026