BeaverDeck logo
BeaverDeck

Home / BeaverDeck / Docs / Insights Guide / Networking Insights / Ingress Backend

Ingress Backend

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 typeingress-backend
Insights sectionNetworking Insights
Alert severityCritical

When It Reports A Finding

An Ingress default backend or HTTP path references a Service name that does not exist in the Ingress namespace.

Why This Is A Problem

The route cannot forward traffic to its intended backend and will normally produce controller errors or failed requests.

Recommended Response

  1. Review every backend Service name in the Ingress rules and default backend.
  2. Create the intended Service or correct stale names in the Ingress manifest.
  3. Then verify Service endpoints so an existing Service also has ready backends.

Scope And Limitations

The check proves only that the Service object exists. Port validity, endpoint readiness, ingress-controller behavior, and application health are separate concerns.

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.