⚠️ Ingress NGINX Project Status Update ⚠️

[strongjz]

We have created a new project, InGate, an Ingress and Gateway API Controller for Kubernetes, discussed at the gateway-api community meeting. In our ingress-nginx KubeCon NA 2024 Maintainer talk, we discussed our path forward for ingress-nginx and future plans for InGate.

What to expect from Ingress-nginx maintainers

• Continued monthly release patches.
  • Golang updates
  • Alpine updates
  • Other 3rd party dependencies
  • CVE patches
  • Bug fixes
• 1.13 in all likelihood will be the last minor release
• Support new Kubernetes releases via our ingress-nginx e2e tests
• No new features from maintainers
  • Features from ingress-nginx community members will be on a case-by-case basis
• Migration path from ingress-nginx to Ingate

Once a stable release of InGate is available we will officially put the project in maintenance mode.

If you have an open ingress-nginx PR, please check it is labeled with a milestone, this indicates we plan to work it into a release and no need to reach out further.

The InGate repo to follow along is in the kubernetes-sigs repo

How to stay informed:

Our ingress-nginx meeting has been moved to monthly and InGate is twice a week.

• InGate Community Meeting Zoom
• InGate Community Meeting Notes
• Slack #ingate-users
• Slack #ingate-dev
• InGate Google Group

If you have any issues or questions, please let us know by commenting here, reaching out in the ingress-nginx monthly community meeting, or slack channel. This whole process of migration to InGate and putting ingress-nginx into maintenance mode will take about 2 years. We will update our communication channels regularly about updates and the status of the project. Please join the InGate, and the Gateway Api community meetings to discuss this further.

Join us in at Kubecon London where we will be discussing more about the project migration, here is the schedule for that talk How to Gateway with Ingress