# Requirement of l5d-dst-override headers in ingress mode

**URL:** <https://linkerd.buoyant.io/t/requirement-of-l5d-dst-override-headers-in-ingress-mode/156>\
**Category:** Linkerd General Discussion\
**Created:** [June 9, 2023, 2:01pm UTC](https://linkerd.buoyant.io/t/requirement-of-l5d-dst-override-headers-in-ingress-mode/156 "2023-06-09T14:01:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![chicocvenancio](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/chicocvenancio/32/95_2.png) [@chicocvenancio](https://linkerd.buoyant.io/u/chicocvenancio)\
**Post date:** [June 9, 2023, 2:01pm UTC](https://linkerd.buoyant.io/t/requirement-of-l5d-dst-override-headers-in-ingress-mode/156/1 "2023-06-09T14:01:18Z")

</div>

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

```auto
status: NotFound, message: "No such service", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "content-length": "0"} } error.sources=[status: NotFound, message: "No such service", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc".

```

[Unexpected behavior change on ingress injected pods in v2.13.x · Issue #10908 · linkerd/linkerd2 · GitHub](https://github.com/linkerd/linkerd2/issues/10908) was created on the premise this was a good, intended change and just improperly documented. I created #1634 with the same premise.

It seems this was a documented change in `edge-21.5.1`, however and reverted in `edge-21.5.3` after [some discussion](https://github.com/linkerd/linkerd2/issues/6157).

One issue with this change is the difficulty that some ingress controllers provide for configuring headers for each service will severely increase the complexity of setting up linkerd. A more intractable issue is the ability to ingress to non-meshed services (including external services).

---

<div class="post-metadata">

**Author:** ![eric\_buoyant](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/eric_buoyant/32/65_2.png) [@eric\_buoyant](https://linkerd.buoyant.io/u/eric_buoyant)\
**Post date:** [June 16, 2023, 12:36am UTC](https://linkerd.buoyant.io/t/requirement-of-l5d-dst-override-headers-in-ingress-mode/156/2 "2023-06-16T00:36:28Z")

</div>

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](https://github.com/linkerd/linkerd2/issues/10908)

---

<div class="post-metadata">

**Author:** ![eric\_buoyant](https://yyz1.discourse-cdn.com/flex029/user_avatar/linkerd.buoyant.io/eric_buoyant/32/65_2.png) [@eric\_buoyant](https://linkerd.buoyant.io/u/eric_buoyant)\
**Post date:** [June 23, 2023, 5:02pm UTC](https://linkerd.buoyant.io/t/requirement-of-l5d-dst-override-headers-in-ingress-mode/156/3 "2023-06-23T17:02:58Z")

</div>

The fix for this has been released with the new stable release 2.13.5 [Release stable-2.13.5 · linkerd/linkerd2 · GitHub](https://github.com/linkerd/linkerd2/releases/tag/stable-2.13.5)