Ingress-nginx final releases

[James Strong]

Folks it has been a wild ride for maintaining such an impactful project. I have learned a lot about OSS and met some incredible people along the way. We have released our final versions to support k8s 1.35 and patch this latest CVE https://github.com/kubernetes/kubernetes/issues/137560 . Unless there are major regressions with this patch, we plan to archive the repo after Kubecon, images and helm charts of released versions will still be available for users.

The Kubernetes SRC will remain the CVE Numbering Authority of scope for issuing CVEs in ingress-nginx code that was written by Kubernetes contributors, and will continue to serve in that capacity. They will not be issuing patch releases for any vulnerabilities reported after EoL, nor responding to other vulnerability-related issues such as CVEs detected in dependencies or release artifacts. If other projects maintain a fork of ingress-nginx, they can request CVE issuance from SRE instead of having to go to MITRE. Per SRC Member @Tabitha Sable

Please join us at Kubecon EU 2026 with Gateway api maintainers to discuss more about the future of Gateway and moving away from ingress https://kccnceu2026.sched.com/event/2EsAI/gateway-api-bridging-the-gap-from-ingress-to-[…]na-lach-rostislav-bobrovsky-google-norwin-schnyder-airlock

Releases:

• https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.15.0
• https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.14.4
• https://github.com/kubernetes/ingress-nginx/releases/tag/controller-v1.13.8

Thank you,

James

[Jeffrey Sica]

A big thank you to James and all the other ingress-nginx maintainers, past and present. 

<3

--
You received this message because you are subscribed to the Google Groups "dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@kubernetes.io.
To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/dbe0e808-9b93-4fac-8fd2-c68ffea8c08en%40kubernetes.io.

[Antonio Ojea]

Respect!!!

To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/CAGPWgfwBYaVkQauAJHAfWdKUQQsOvecpr5Vcy9KVRSuczc%2BADA%40mail.gmail.com.

[Tim Hockin]

100%

Thank you for all you folks have done.

To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/CAAdXToRBXV_8Z04-qVtouh5En0ccdNE8Z-U2gnkZ4KTKwGahwg%40mail.gmail.com.

[Benjamin Elder]

Thank you all.

To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/CAO_RewZY5gyUf8nM2-XEfB%3Dj%2BmhPpZC_n6Q-XWyhCS49q5k-oA%40mail.gmail.com.

[Mario Fahlandt]

Thank you, James, for all the work and all the other maintainers of ingress-nginx in the past and present. Also for the attempts to find new maintainers since KubeCon Chicago! 

[Michal Wysokinski]

Thanks James and to all other folks and congratulations for the awesome work! ingress-nginx has always been my "go-to" because it just worked!

To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/3bc64a4b-dc0e-49f0-ba8f-bb420227444cn%40kubernetes.io.