BeaverDeck logo
BeaverDeck

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

Service Coverage

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 typeservice-coverage
Insights sectionNetworking Insights
Alert severityWarning

When It Reports A Finding

No Service selector matches the pod-template labels of a Deployment or StatefulSet.

Why This Is A Problem

A workload intended to receive stable in-cluster traffic may be unreachable because no Service selects its pods.

Recommended Response

  1. Confirm whether the workload is expected to receive network traffic through a Service.
  2. If it is, create a Service or correct its selector to match the workload's pod-template labels.
  3. Verify the resulting EndpointSlices and ready endpoints.

Scope And Limitations

Not every Deployment or StatefulSet needs a Service. Workers, one-way consumers, and some controllers can be intentionally private; suppress the finding only after confirming that design.

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.