Gateway API Stuck in ‘Pending’ State with AWS ALB Controller on EKS 1.31 (Works with NGINX Ingress)

[felipemoskit]

Describe the bug
I am trying to configure the Gateway API using the AWS ALB Controller, but the Gateway remains stuck in a “Pending” state. When I switch to the NGINX Ingress Controller, it works as expected. However, due to our environment’s standardization, we would prefer to use the AWS ALB Controller. I have read some older issues regarding this configuration, but I would like to confirm if the ALB Controller already supports installation and configuration for the Gateway API or if it is still not fully supported.

Steps to reproduce

Install the AWS ALB Controller (version 2.10.1).
Deploy the Gateway API resources on an EKS cluster running version 1.31.
Observe that the Gateway remains in a “Pending” state and never becomes active.
Expected outcome
The Gateway API should be successfully installed and configured using the AWS ALB Controller, transitioning to an active/healthy state without getting stuck in “Pending.”

Environment

AWS Load Balancer Controller version: 2.10.1
Kubernetes version: 1.31
EKS (yes/no): Yes, EKS version 1.31
Additional context
Any help or guidance on this matter would be appreciated. Thank you!

[zac-nixon]

Gateway API is not currently supported by the controller but we are actively working on it.
#1338