ALB not deleted after changing group.name

[ecerulm]

Describe the bug

aws-load-balancer-controller 2.7.1

I had an ingress that did not have any alb.ingress.kubernetes.io/group.name annotation.
I add the alb.ingress.kubernetes.io/group.name annotation to the Ingress.
A new ALB is created.
The old ALB is not deleted.

I though the

If an IngressGroup no longer contains any Ingresses, the ALB for that IngressGroup will be deleted and any deletion protection of that ALB will be ignored.

meant that the "implicit IngressGroup" that existed before will be deleted now that it's empy.

Steps to reproduce

Expected outcome

The old ALB should be deleted.

Environment

• AWS Load Balancer controller version: 2.7.1
• Kubernetes version: 1.29
• Using EKS (yes/no), if so version? eks 1.29

Additional Context:

[ecerulm]

The tags on the "old" ALB

Key	Value
elbv2.k8s.aws/cluster	XXXX
ingress.k8s.aws/resource	LoadBalancer
ingress.k8s.aws/stack	airflow/airflow-ingress
Name	airflow-webserver

The tags on the "new" (group.name) ALB:

Key	Value
elbv2.k8s.aws/cluster	XXXX
ingress.k8s.aws/resource	LoadBalancer
ingress.k8s.aws/stack	thegroupname
Name	airflow-webserver