Update README.md to announce the upcoming EOL

[venkatamutyala]

per https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/ this is a request to have the README.md updated to announce the EOL.

A clear announcement will prevent new adopters from creating tech debt and having to migrate to Gateway API or another ingress controller in 4 months.

edited:

• added links and cleaned up wording

[k8s-ci-robot]

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.

[pascal-hofmann]

@venkatamutyala I think the issue was unpinned, because InGate is also dead. So it makes no sense to point to it.

[avin-kavish]

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.

[miraculixx]

For anyone wondering what this is about:
https://www.kubernetes.dev/blog/2025/11/12/ingress-nginx-retirement/

[rittneje]

There should also be a pinned issue announcing the EOL.

[Gacko]

@strongjz and me are already working on the needed changes.