⚠️ Maintenance Mode — Forkline Maintained ForkThis is a maintained fork of the retired Kubernetes ingress-nginx controller, kept in strict maintenance mode: no new features, no behavior changes — only dependency updates and security patches. We use date-based versioning (e.g.,
v2026.5.3) since semantic versioning has no meaning when there are no features or breaking changes.For new deployments, consider Gateway API implementations instead. This fork serves existing ingress-nginx users who need continued maintenance.
Maintained by Forkline using coding-agent orchestration — automated but never unattended.
Upstream Retirement Context
What You Need to Know about Ingress NGINX Retirement:
- Best-effort maintenance continued until March 2026.
- Upstream no longer provides releases, bugfixes, or security updates.
- Existing deployments and historical artifacts remain important for operators and forks like this one.
Overview
ingress-nginx was an Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer.
Learn more about Ingress on the Kubernetes documentation site.
Usage warnings
Do not use in multi-tenant Kubernetes production installations. This project assumes that users that can create Ingress objects are administrators of the cluster. See the FAQ for more.
Troubleshooting
If you encounter issues, review the troubleshooting docs, search for an issue, or talk to us on the #ingress-nginx-users channel on the Kubernetes Slack server.
Changelog
See the list of releases for all changes.
For detailed changes for each release, please check the changelog-$version.md file for the release version.
For detailed changes on the ingress-nginx helm chart, please check the changelog folder for a specific version.
CHANGELOG-$current-version.md file.
Supported Versions table
All images use unified date-based versioning. The version indicates when the software was last maintained.
| Supported | Ingress-NGINX version | k8s supported version | Alpine Version | NGINX Version | Helm Chart Version |
|---|---|---|---|---|---|
| ✅ | v2026.5.3 | 1.35, 1.34, 1.33, 1.32, 1.31 | 3.23.4 | 1.27.1 | 2026.5.3 |
| 🔄 | v2026.5.2-1 | 1.35, 1.34, 1.33, 1.32, 1.31 | 3.23.4 | 1.27.1 | 2026.5.2-1 |
| 🔄 | v2026.5.2 | 1.35, 1.34, 1.33, 1.32, 1.31 | 3.23.4 | 1.27.1 | 2026.5.2 |
| 🔄 | v2026.4.3-1 | 1.35, 1.34, 1.33, 1.32, 1.31 | 3.23.4 | 1.27.1 | 2026.4.3-1 |
| 🔄 | v2026.4.3 | 1.35, 1.34, 1.33, 1.32, 1.31 | 3.23.3 | 1.27.1 | 2026.4.3 |
Get Involved
Thanks for taking the time to join our community and start contributing!
-
This project adheres to the Kubernetes Community Code of Conduct. By participating in this project, you agree to abide by its terms.
-
Contributing: Documentation contributions are welcome.
- Read
CONTRIBUTING.mdfor information about the workflow that we expect and instructions on the developer certificate of origin that we require. - Join our Kubernetes Slack channel for developer discussion : #ingress-nginx-dev.
- Submit GitHub issues for documentation problems.
- Please make sure to read the Issue Reporting Checklist before opening an issue. Issues not conforming to the guidelines may be closed immediately.
- Read
-
Support:
- Join the #ingress-nginx-users channel inside the Kubernetes Slack to ask questions or get support from the maintainers and other users.
- The GitHub issues in the repository are exclusively for bug reports and feature requests.