Cannot change AWS NLB target group type from instance to ip for EKS Fargate Cluster

[stevenho1102]

Is your enhancement request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When I deploy a Gateway with listeners HTTP, Port 80, a AWS NLB was provisioned. However the target group type is instance, it caused not able to register the Gateway fargate pod.

What would you like to be added:
A clear and concise description of what you would like to be added.
When I use Ingress Nginx controller, I can add these annotations for the AWS NLB configuration.

annotations = {
"service.beta.kubernetes.io/aws-load-balancer-internal" = "true"
"service.beta.kubernetes.io/aws-load-balancer-type" = "nlb"
"service.beta.kubernetes.io/aws-load-balancer-backend-protocol" = "tcp"
"service.beta.kubernetes.io/aws-load-balancer-nlb-target-type" = "ip"
"service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled" = "true"
"service.beta.kubernetes.io/aws-load-balancer-ssl-ports" = "443"
"service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy" = "ELBSecurityPolicy-TLS13-1-2-2021-06"
"service.beta.kubernetes.io/aws-load-balancer-ssl-cert" = "arn:aws:acm:us-west-1:11561516616:certificate/hfiwyrrhwifheoth32"
}

Why this is needed:
Explain why this enhancement is needed.
Without this, the traffic cannot flow from AWS NLB to my application through the Nginx.

Additional context
Add any other context or screenshots about the enhancement request here.

[nginx-bot]

Hi @stevenho1102! Welcome to the project! 🎉

Thanks for opening this issue!
Be sure to check out our Contributing Guidelines and the Issue Lifecycle while you wait for someone on the team to take a look at this.

[sjberman]

Hi @stevenho1102, see my comment here on a similar issue. Let me know if that helps.