In the process of configuring Layer 4 load balancing using Annotation, the "loadbalancer for service not found, but the status.LoadBalancer.Ingress not nil, it may be caused by lb deleted" event is reported.

Cause analysis

This event indicates that the Service has already been associated with a CLB instance. Possible reasons are as follows:

service.beta.kubernetes.io/system-volcengine-loadbalancer-create-response-id or service.beta.kubernetes.io/volcengine-loadbalancer-id was changed to a non-existent CLB instance ID.

The CLB instance was accidentally deleted.

Solution

Check whether the CLB instance ID specified in service.beta.kubernetes.io/system-volcengine-loadbalancer-create-response-id or service.beta.kubernetes.io/volcengine-loadbalancer-id exists.

If the CLB instance does not exist or was accidentally deleted, log in to the Load Balancer console to re-create the CLB instance, or directly use the load balancer created by Annotation and create a LoadBalancer Service. For details, see Configuring CLB LoadBalancer Services by using annotations.

Last updated: 2026.07.23 14:31:46

Public security network record in Beijing: No. 11010802032137