Kevin Leimkuhler

Turns out we already should be handling this, but it's a subtle difference between the `linkerd-config` ConfigMap's `ClusterDomain` and `IdentityTrustDomain` fields. Because we are using the gateway's identity here, we...

Moving this out of the milestone for now until we hear back more about the situation described. I answered with the details provided, but unfortunately it's not been easy to...

@joewilliams Sorry there has been no response on this. We'll make sure to discuss and consider options to solve this issue and your linked discussion. For your `l5d-forwarded-for` example, what...

Hey @dwilliams782 thanks for the investigation and updates on this. I attempted to reproduce this today without luck. I'm going to read through things again to make sure I didn't...

To be clear, I do think there is a bug here in the destination service given that you can create two Services that target the same DaemonSet, and one stays...

@eugenepaniot In the destination logs that you posted above, had you made any code changes or is it from an edge release version? I see the original issue was using...

Ok thanks for the update on this. Sounds like a lot has a changed on your end; glad to hear it sounds like things are stable for you now but...

That'd be great @Santosh1176! Let us know if you need any help.

You're going to need multicluster setup to test this properly. The `gateways` command will only have stats when the current cluster is linked to another. You may be able to...

I'd recommend upgrading to the latest stable 2.11.4. While I can't be sure, this does look like an issue that has already been fixed by linkerd/linkerd2-proxy#1670. If you continue to...