ask for Kubernetes 1.35 support in ingress-nginx

[corlandini]

Hi team,

We are currently planning an upgrade of our AKS clusters to Kubernetes 1.35.
We noticed that the latest ingress-nginx release does not list Kubernetes 1.35
in the supported version matrix.

Before proceeding with our upgrade strategy, we would like to clarify:

1. Is support for Kubernetes 1.35 already planned for an upcoming release?
2. Is there an expected timeline or target version for official 1.35 compatibility?
3. Is there any known limitation blocking ingress-nginx on Kubernetes 1.35 at this time?

We deploy ingress-nginx via the official Helm repository:
https://kubernetes.github.io/ingress-nginx

Any guidance would help us plan our upgrade path safely.

Thanks!

[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.

Details

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.

[Gacko]

We already support v1.35 on our main branch, but since it was released after we released v1.14, we could not include it there. Also we won't add support to v1.14, as this is more than a patch-level change.

So v1.35 will be supported with an upcoming v1.15. We are currently working on v1.14.2, v1.14.3 will be released beginning of February, so v1.15 will get released together with v1.14.4 beginning of March.

[Gacko]

However, "support" only means our CI runs tests against a KIND v1.35 node, which does not really compare to a real AKS cluster.

Long story short: If you want to verify Ingress NGINX is working with AKS v1.35, then simply execute our E2E test suites against your cluster.