Tap Service Unresponsive Blocking Traffic Inspection
warningreliabilityUpdated Feb 23, 2026
The Linkerd tap service may fail to respond to live traffic inspection requests, eliminating critical debugging visibility. Often caused by tap pod crashes, network policy blocks, or resource constraints.
Technologies:
How to detect:
Detect when 'linkerd tap' commands hang, timeout, or return 'service not responding' errors. Check tap service pod status and resource allocation in the linkerd namespace.
Recommended action:
Verify tap service pod is running with 'kubectl get pods -n linkerd'. Check tap pod logs for errors. Review network policies allowing traffic to tap service. Assess and increase CPU/memory allocations if resource-constrained. Validate tap service endpoints are reachable.