Home / BeaverDeck / Docs / Insights Guide / Networking Insights / LoadBalancer

LoadBalancer

BeaverDeck uses this check to identify a specific networking condition that may need operator review.

Permissions: viewing checks requires insights: view. Opening a linked object or logs requires the corresponding resource permission, and the BeaverDeck ServiceAccount must be allowed to read the Kubernetes resources used by the check. Suppressing a finding requires insights: edit and affects all users.

Check type	`loadbalancer-pending`
Insights section	Networking Insights
Alert severity	Warning

When It Reports A Finding

A Service has type LoadBalancer but its status contains no external ingress address.

Why This Is A Problem

External clients cannot reach the Service through the expected load balancer until the controller or provider assigns an address.

Recommended Response

Review Service events and cloud or load-balancer controller logs.
Check annotations, ingress class or provider settings, quotas, permissions, subnet capacity, and address allocation.
Correct the provider-specific configuration and wait for an address to appear in Service status.

Scope And Limitations

There is no age threshold. A newly created Service can show a normal provisioning delay, and bare-metal clusters require an appropriate LoadBalancer implementation.

After remediation: refresh Networking Insights and verify the underlying resource or metric. Suppress the finding only when the condition is intentional and its risk is accepted.