kubernetes
So long, and thanks for all the fish
Just wanted to drop a BIG thank you to all previous and current maintainers / contributors as well as to the sig-network group for the work on the ingress-nginx controller.
It had its issues and one could have opinions about one or the other thing, but in the grand scheme of things it was a reliable component like a non destructible tractor (I mean this in a good positive way). One knew how it worked, how it behaved, and it was easy to wrap one’s head around its functionality.
Again, thank you for all the hard work and effort. 🙏
Cheers.
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
I don't know the exact issues causing this but nginx ingress powers a lot of clusters and there's no consensus that it's bad and needs to migrated away from.
I'll be maintaining a fork here: https://github.com/viduli-io/ingress-nginx
We are using it and haven't encountered a reason to migrate away thus far.
I'll be maintaining a fork here: https://github.com/viduli-io/ingress-nginx
Thank you for this 🙏
Thank you, guys! This really means a lot to us!
Also thank you @avin-kavish for being an example of how people can deal with this situation!
What happened?
NVM: https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/
Yes, thank you everybody for this project, it has served us so well!
This piece of software is too much used, everywhere, I think it is possible to find companies to pay for maintenance of this project.
I'm trying something with my little contacts..
I think it is possible to extend maintenance and support for some months, maybe years, to give enterprises a bit more time to move.
I have 2 questions:
- let's say at least 2 companies are willing to step up and take the responsibility of the project, what would be required to take over the responsibility of this repo and all the related infra?
- are current contributors available for hire? or not at all?
Ok, one last question :) who's going to fosdem to have a drink somewhere and discuss about that? :)
The EmeritOSS fork might also be relevant: https://www.zdnet.com/article/chainguard-emeritoss-support-for-abandoned-open-source-programs/
