Kubernetes Ingress deprecation impact on AWS Load Balancer Controller (ALB) usage

[dhineshbabuelango]

I am currently running an Amazon EKS cluster and using the AWS Load Balancer Controller to provision Application Load Balancers (ALB).
Ingress resources (kind: Ingress) are used to define HTTP(S) routing rules for applications.

There has been discussion in the Kubernetes ecosystem about Ingress deprecation, particularly around Ingress-NGINX and the long-term move towards Gateway API. This has raised some confusion around the future viability of kind: Ingress in general.

My intent is to clarify the following points:

Does the Ingress deprecation only apply to Ingress-NGINX (the ingress controller), or does it also apply to:

The Ingress API (kind: Ingress) itself, when used with the AWS Load Balancer Controller?

Specifically, can users:

Continue using kind: Ingress with the AWS Load Balancer Controller for ALB-based routing without any immediate or medium-term concerns?

Or is there an expectation that users must migrate to API Gateway or Gateway API once Ingress is deprecated?

Given that Gateway API is not yet fully supported by the AWS Load Balancer Controller:

Is kind: Ingress still considered the recommended and supported approach for ALB-based ingress on EKS?

Are there any timelines or guidance for migration that users should be aware of?

In summary, I want to confirm whether:

The deprecation concerns are specific to ingress-nginx as an implementation, and

Do not affect ALB-based ingress routing using the AWS Load Balancer Controller, which still relies on kind: Ingress.

Any clarification or official guidance on this would be greatly appreciated.