Hi everyone, I decided to step down as maintainer of the project after the next release.
I would really love to find new maintainer/s to take over responsibility for this project.
Anyone up for the challenge?
@aledbf Thank you very much for your work. nginx-ingress is a great piece of software. You will be missed.
@aledbf Thank you so much for your hard work and assistance throughout the years. You've been a huge help to me personally on many occasions, and I'm very grateful. Please let me know how I can buy you a drink.
Thank you for everything! This responsibility was nothing slight, and the community and world are better off for what you've contributed as a maintainer
We've been using nginx-ingress in production for the past 2.5 years - since the early days when it shared the repo with the GCP ingress. Thank you for everything!
Hello (and hi @aledbf!),
I have not been involved with the NGINX Ingress Controller so far, but I vividly support all projects using OpenResty (of which I am a maintainer). @aledbf and I have briefly met in person a few times when he started the Kong Ingress Controller last year (which is also based upon OpenResty).
I do not have a lot of time to dedicate to this project (nor do I have experience contributing to it), but I will happily assist with any OpenResty/NGINX/LuaJIT related topic if anybody thinks that'd be helpful (PR reviews, questions, minimal patches, etc...). Feel free to reach out at thibault [at] konghq.com or ping me on GitHub if needed.
Best,
@aledbf Thank you very much for hard work on this!
I didn't have a chance to contribute to the project before, but if I can help somehow - let me know :)
@aledbf thank you so much for your leadership and contributions to ingress-nginx! :)
Just notice this "news".
Thank you @aledbf for all amazing you have done.
You also gave me several times of help in different repo/channel.
Thank you again in ingress-nginx !
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Most helpful comment
@aledbf Thank you so much for your hard work and assistance throughout the years. You've been a huge help to me personally on many occasions, and I'm very grateful. Please let me know how I can buy you a drink.