The 2.13.0 release seems to have brought the hard requirement of l5d-dst-override headers in all requests going to a pod meshed in ingress mode. Requests without it return a 502 and output a message similar to status: NotFound, message: "No such service", details: [], metadata: MetadataMap { heade…

Thanks for reaching out! We’re currently working on a fix for this here: Unexpected behavior change on ingress injected pods in v2.13.x · Issue #10908 · linkerd/linkerd2 · GitHub

Requirement of l5d-dst-override headers in ingress mode

Linkerd General Discussion

eric_buoyant June 23, 2023, 5:02pm 3

The fix for this has been released with the new stable release 2.13.5 Release stable-2.13.5 · linkerd/linkerd2 · GitHub

Topic		Replies	Views
Linkerd , traefik and opaque ports Linkerd General Discussion proxy , configuration , ingress	1	501	March 21, 2024
HTTPRoute not working on subsequent calls Linkerd General Discussion proxy , configuration	6	1260	September 28, 2023
Meshed pods fail to connect to unmeshed smtp/redis pods with Linkerd 2.14.2 Linkerd General Discussion	10	1788	November 9, 2023
2.13.0 - Request failed error = no route found for request Linkerd General Discussion	5	872	April 21, 2023
Custom headers being stripped before reaching application - is this expected? Linkerd General Discussion proxy , configuration	3	78	November 3, 2025

Requirement of l5d-dst-override headers in ingress mode

Related topics