Ingress NGINX (ingress-nginx) End of Life: Retired March 2026
ingress-nginx, the Kubernetes community ingress controller (kubernetes/ingress-nginx), reached end of life in March 2026, when the Kubernetes project retired it: no further releases, no bugfixes and no security updates. Its last releases were published on March 19, 2026. GitHub shows the repository as archived and read-only since March 24, 2026. Kubernetes SIG Network and the Security Response Committee announced the retirement on November 11, 2025. Existing deployments keep working, and the Helm charts and container images remain available. The project's advice is to move to Gateway API or to another Ingress controller.
Key Dates at a Glance
- ingress-nginx: retirement announced 2025-11-11
- ingress-nginx: Steering Committee and Security Response Committee statement 2026-01-29
- ingress-nginx: last releases published 2026-03-19
- ingress-nginx: end of life (retired, best-effort maintenance ended) 2026-03
- ingress-nginx: repository archived and read-only 2026-03-24
Timeline: from the announcement to a read-only repository
| When | What happened | Where it is printed |
|---|---|---|
| November 11, 2025 | Kubernetes SIG Network and the Security Response Committee announced the retirement. Best-effort maintenance was to continue until March 2026. | Kubernetes blog |
| January 29, 2026 | The Kubernetes Steering Committee and Security Response Committee issued a joint statement telling users to check their clusters and begin migrating. | Kubernetes blog |
| March 19, 2026 | Last releases published: three controller releases and their Helm charts. | GitHub releases page |
| March 2026 | The retirement month. Best-effort maintenance ended. The project printed the month only, with no day. | Kubernetes blog |
| March 24, 2026 | The repository was archived by its owner. It has been read-only from that day. | GitHub repository banner |
The Kubernetes project calls this a retirement. Its pages do not use the phrase "end of life". On this site the end-of-life date of ingress-nginx is the retirement month the project announced, March 2026. One note on the first row: the post on the Kubernetes blog is dated November 11, 2025. The copy on the Kubernetes contributor site, which the blog calls the original article, is dated November 12, 2025. The wording is the same.
What the Kubernetes project said, in its own words
The announcement is the post Ingress NGINX Retirement: What You Need to Know on the Kubernetes blog. It describes two phases and makes two promises.
- Until March 2026: best-effort maintenance. The post says: "Best-effort maintenance will continue until March 2026." It gives the month and no day.
- After that: nothing new. The post says there will be "no further releases, no bugfixes, and no updates to resolve any security vulnerabilities" that may be discovered.
- The repositories. The post says the GitHub repositories will be made read-only and left available for reference.
- What keeps working. The post says existing deployments will not be broken, and that existing project artifacts such as Helm charts and container images will remain available.
The post also gives the reason. For years the project had one or two people doing the development work, on their own time. Features that were once useful, such as the "snippets" annotations that add arbitrary NGINX configuration, had come to be treated as serious security flaws. SIG Network and the Security Response Committee wrote that they had exhausted their efforts to find additional support for the project.
The joint statement of January 29, 2026, from the Kubernetes Steering Committee and the Security Response Committee, repeated the same terms more bluntly. It says there will be no more releases for bug fixes, security patches or updates of any kind after the project is retired, and that staying on Ingress NGINX after its retirement "leaves you and your users vulnerable to attack".
What happened in March 2026
The project's GitHub pages show how the retirement was carried out.
- The last releases. The releases page lists three controller releases published on March 19, 2026: v1.15.1, v1.14.5 and v1.13.9, with Helm charts 4.15.1, 4.14.5 and 4.13.9. Nothing is listed after them. The release notes for v1.15.1 list dependency, image and test updates.
- The archive. GitHub's banner on the repository says it was archived by the owner on Mar 24, 2026 and is now read-only. An archived repository takes no new commits, issues or pull requests.
- Where it is. The repository is still at github.com/kubernetes/ingress-nginx. It was archived in place.
- The README. It opens with a section headed "Ingress NGINX Retirement" that repeats the terms of the announcement. Its overview is in the past tense: "ingress-nginx was an Ingress controller for Kubernetes". It tells anyone not already using ingress-nginx not to deploy it, and to choose a Gateway API implementation.
- The documentation. The project's documentation site is still online, with the same retirement notice at the top.
ingress-nginx is not NGINX Ingress Controller from F5
Two different ingress controllers have nearly the same name. Only one of them was retired.
| Question | ingress-nginx | NGINX Ingress Controller |
|---|---|---|
| Who makes it | The Kubernetes community | F5 |
| Repository on GitHub | kubernetes/ingress-nginx | nginx/kubernetes-ingress |
| Other names in use | Ingress NGINX, Ingress-NGINX | NGINX Ingress, NGINX Ingress Controller for Kubernetes |
| Covered by the Kubernetes retirement | Yes | No |
| Repository state | Public archive, read-only | Public, not archived |
The Kubernetes blog makes the same distinction. Its post Before You Migrate says that Ingress-NGINX and NGINX Ingress are "two separate Ingress controllers": the first is maintained and governed by the Kubernetes community, the second is an Ingress controller by F5, and they both use NGINX but are otherwise unrelated.
To see which one a cluster runs, look at what is deployed. The check the Kubernetes project gives for ingress-nginx is this command, run with cluster administrator permissions:
kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx
The project's release notes name its controller image as registry.k8s.io/ingress-nginx/controller, and its annotations start with nginx.ingress.kubernetes.io/. If the pods, the image and the annotations in a cluster match those, it runs the retired controller. For the support status of NGINX Ingress Controller, F5's own pages are the source. We do not track that product.
What the retirement does not change
- Running clusters keep running. Nothing was switched off. The January statement warns that this is the risk: existing deployments continue to work, so a team that does not check may not know it is affected.
- The artifacts are still there. The announcement says the Helm charts and container images remain available.
- The Ingress API is not retired. The Kubernetes documentation says the Ingress API has been frozen: it stays generally available, the project has no plans to remove it, and it gets no further changes. What was retired is one controller that implements that API.
What did change is who fixes the next flaw. The project's answer is that it publishes no updates for vulnerabilities found after March 2026, in a component that sits at the edge of the cluster and handles traffic from outside it.
The path forward the project names
- Gateway API. The announcement calls Gateway API "the modern replacement for Ingress" and recommends it first. The README says the same: choose a Gateway API implementation.
- Another Ingress controller. For teams that must stay on the Ingress API, the announcement points to the list of Ingress controllers in the Kubernetes documentation. It names no single replacement. That page says Kubernetes as a project supports and maintains the AWS and GCE controllers, and lists third-party controllers that the project says it is not responsible for.
- Ingress2Gateway. SIG Network publishes a migration tool and announced its 1.0 release on the Kubernetes blog. It translates Ingress resources and many ingress-nginx annotations to Gateway API, and warns about configuration it cannot translate. The post describes it as a migration assistant, not a one-shot replacement.
The Steering Committee statement is plain about the cost: "None of the available alternatives are direct drop-in replacements." It says the move will take planning and engineering time. The announcement also says that InGate, the controller once planned as the successor, never reached maturity and would be retired too.
What to do if a cluster still runs ingress-nginx
- Find it. Run the
kubectlcommand above on every cluster. The announcement notes that Ingress NGINX is deployed as part of many hosted Kubernetes platforms, so a team can be running it without having chosen it. - Note the release. The last controller releases on the project's releases page are v1.15.1, v1.14.5 and v1.13.9. A cluster on an older release is behind the last state the project published.
- Check the Kubernetes version. The README's Supported Versions table lists the Kubernetes versions each release passed the project's end-to-end tests on. Its v1.15.1 row lists Kubernetes 1.35, 1.34, 1.33, 1.32 and 1.31. No version newer than Kubernetes 1.35 appears in the table. Kubernetes 1.35's own end-of-life date is February 28, 2027; after it, every Kubernetes version the project tested ingress-nginx on is past end of life. Our Kubernetes page has the dates for each version.
- Choose the target. Gateway API or another Ingress controller, as the project advises. Read the Before You Migrate post first: it lists five ingress-nginx behaviors that a straight translation can get wrong.
- Check the support dates of whatever replaces it. A replacement has a lifecycle of its own. We track several of the projects on the Kubernetes documentation list, among them Cilium, Contour, Istio and Traefik. Being on that list is not a recommendation, from Kubernetes or from us.
- If the move cannot happen yet. The project offers nothing further. Treat the controller as unmaintained software at the cluster edge, and read the README's usage warning: it says not to use ingress-nginx in multi-tenant production installations, because the project assumes that anyone who can create Ingress objects is a cluster administrator.
The EOL Checker looks up one product and version. Our Ingress NGINX page carries the same dates as this guide.
Frequently Asked Questions
When did ingress-nginx reach end of life?
March 2026. The Kubernetes project announced on November 11, 2025 that best-effort maintenance would continue until March 2026, with no further releases, bugfixes or security updates afterward. The last releases were published on March 19, 2026, and the repository has been archived and read-only since March 24, 2026.
Is ingress-nginx still maintained after March 2026?
No. The Kubernetes project retired it. Its announcement says that after March 2026 there are no further releases, no bugfixes and no updates to resolve security vulnerabilities that may be discovered. Existing deployments keep working, and the Helm charts and container images remain available.
What was the last ingress-nginx release?
The releases page of kubernetes/ingress-nginx lists controller v1.15.1, v1.14.5 and v1.13.9, all published on March 19, 2026, as its last releases. Nothing is listed after them.
Is the ingress-nginx repository archived?
Yes. GitHub shows kubernetes/ingress-nginx as archived by its owner on March 24, 2026, and read-only. The code, the releases and the documentation remain available for reference.
Is NGINX Ingress Controller from F5 retired too?
No. The retirement covers ingress-nginx, the controller maintained by the Kubernetes community. NGINX Ingress Controller is a different product, made by F5, in its own repository (nginx/kubernetes-ingress), which is not archived. The Kubernetes blog describes the two as separate controllers that both use NGINX but are otherwise unrelated.
Is the Kubernetes Ingress API going away?
No. The Kubernetes documentation says the Ingress API has been frozen: it remains generally available, the project has no plans to remove it, and it gets no further changes. What was retired is one controller that implements the API.
What replaces ingress-nginx?
The project names Gateway API, which its announcement calls the modern replacement for Ingress, or another Ingress controller from the list in the Kubernetes documentation. The Steering Committee statement of January 29, 2026 says none of the alternatives is a drop-in replacement, so the move needs planning and testing.
Related
- Ingress NGINX — live status and EOL Risk Score
- Kubernetes end of life — every Kubernetes version and its dates
- Kubernetes — the version table
- EOL Checker
- How we verify our dates