BeaverDeck logo
BeaverDeck

Home / BeaverDeck / Docs / Insights Guide / Networking Insights / Ingress Route Collision

Ingress Route Collision

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-route-collision
Insights sectionNetworking Insights
Alert severityWarning

When It Reports A Finding

Two or more Ingress resources claim the same ingress class, host, and path. Empty hosts are treated as * and empty paths as /.

Why This Is A Problem

Controller-specific conflict resolution can make routing unpredictable and cause one application to shadow another.

Recommended Response

  1. Review every Ingress listed for the conflicting class, host, and path.
  2. Consolidate ownership or assign distinct hosts, paths, or ingress classes.
  3. Check the ingress controller's generated configuration and route behavior after the change.

Scope And Limitations

The key does not include pathType or controller-specific annotations. Some controllers intentionally merge compatible Ingress resources, so validate expected controller behavior.

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.