Ingress NGINX Retirement

Retiring

What You Need to Know about Ingress NGINX Retirement:

• Best-effort maintenance will continue until March 2026.
• Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered.
• Existing deployments of Ingress NGINX will not be broken.
  • Existing project artifacts such as Helm charts and container images will remain available.

Ingress NGINX Controller

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

If you are not already using ingress-nginx, you should not be deploying it as it is not being developed. Instead you should identify a Gateway API implementation and use it.

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

Supported versions for the ingress-nginx project mean that we have completed E2E tests, and they are passing for the versions listed. Ingress-Nginx versions may work on older versions, but the project does not make that guarantee.

See Updating NGINX-Ingress to use the stable Ingress API (July 26, 2021) to upgrade to the stable Ingress API before upgrading to Kubernetes 1.22.

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.md for 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.

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

License

Apache License 2.0