Set service status for pre existing ALB

[KarstenSiemer]

Describe the bug
When using a pre-existing ALB and using target group bindings to bind it to a service ( e.g. ingress-nginx ) the status.loadbalancer.ingress fields of the service are not updated.
It looks like ALB type loadbalancer will only update status.loadbalancer.ingress of type ingress resources, but it would make sense to automatically update service fields as well, like with nlb.

In my setup I've been using NLBs for interfacing ingress-nginx and want keep the same characteristics of this approach inside k8s, like ingress classes and not having to annotate ingresses. Yet NLBs lack any type of rate-limiting, which is why I'd like to switch to ALBs.

I also noticed, that I cannot make the controller stop creating security group rules by annotating the service with the annotation
service.beta.kubernetes.io/aws-load-balancer-manage-backend-security-group-rules: "false"

Steps to reproduce

Create ALB with security group and create listeners and target groups.
Create a service and target group bindings.
The service will not receive status.loadbalancer.ingress fields.

Expected outcome
Since the service is bound to the target groups, I'd like to somehow have the controller to add the hostname of the ALB into status.loadbalancer.ingress

Environment

• AWS Load Balancer controller version
  v2.6.1
• Kubernetes version
  v1.26
• Using EKS (yes/no), if so version?
  v1.26.10-eks-4f4795d

Additional Context: