-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Open
Description
Info:
helm chart version: 1.14.0
load-balancer-controller version: public.ecr.aws/eks/aws-load-balancer-controller:v2.14.0
Kubernetes version: EKS v1.32
My load-balancer-controller keeps on trying to delete / reclaim an existing NLB. The logs looks something like this (edited to change service names):
{ "level": "info", "ts": "2025-11-26T20:09:53Z", "logger": "controllers.service", "msg": "successfully built model", "model": "{\"id\":\"org/service\",\"resources\":{}}" }
{ "level": "info", "ts": "2025-11-26T20:09:54Z", "logger": "controllers.service", "msg": "deleting loadBalancer", "arn": "arn:aws:elasticloadbalancing:us-east-1:account:loadbalancer/net/k8s-org-service/id" }
{ "level": "error", "ts": "2025-11-26T20:09:54Z", "msg": "Reconciler error", "controller": "service", "namespace": "org", "name": "service", "reconcileID": "f7711e63-9789-46c9-aa9b-0215e5ee9711", "error": "operation error Elastic Load Balancing v2: DeleteLoadBalancer, https response error StatusCode: 400, RequestID: c00bf50d-8e7c-47b6-8d6b-186b04a2240d, ResourceInUse: Load balancer 'arn:aws:elasticloadbalancing:us-east-1:account:loadbalancer/net/k8s-org-service-id' cannot be deleted because it is currently associated with another service" }
The NLB belongs to service A and there should be no need to recreate the load balancer. It's unclear to me why it wants to delete it. Expected behaviour is that the controller ignore it.
Am I missing an annotation on the service? I have the following annotations:
service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip
service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: ip
Do I have to specify the NLB ARN as well?
Metadata
Metadata
Assignees
Labels
No labels