Home / BeaverDeck / Docs / Insights Guide / Networking Insights / Service Endpoints

Service Endpoints

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	`service-endpoints`
Insights section	Networking Insights
Alert severity	Warning

When It Reports A Finding

A selector-backed Service has zero ready endpoints in its EndpointSlices.

Why This Is A Problem

Traffic sent to the Service has no ready pod backend and will fail or be dropped.

Recommended Response

Compare the Service selector with pod labels and verify that matching pods exist.
Inspect pod readiness, container health, ports, EndpointSlices, and namespace placement.
Fix selectors or workload readiness and confirm at least one ready endpoint appears.

Scope And Limitations

ExternalName Services and Services without selectors are treated as not requiring pod endpoints. Manually managed endpoints must be validated separately.

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.