Alex Leong

I don't think I agree with the premise here that using TrafficSplits to implement failover is unintended, non-standard, or an abuse of the standard. A TrafficSplit is a declarative representation...

I have not been able to reproduce this issue by following the steps here: https://linkerd.io/2.11/tasks/distributed-tracing/ using Linkerd stable 2.11.2. I do not have access to a GKE private cluster to...

Hi @michalschott! If the networks section of a ServerAuthorization is unspecified, it uses Linkerd's cluster networks which are "10.0.0.0/8,100.64.0.0/10,172.16.0.0/12,192.168.0.0/16" by default. If you have pods in other networks, you'll want...

Linkerd does not support printing the message bodies in tap, but this is something that's certainly on the long-term roadmap. The work to add this feature has not yet been...

Adding a `dst_target_port` metric doesn't seem unreasonable to me.

Hi @mohitreddy1996. Based on what you've described here, I suspect something is strange with your environment where this isn't working. ``` [ 27936.615209s] INFO ThreadId(01) inbound: linkerd_app_core::serve: Connection closed error=a...

@mohitreddy1996 I'd recommend investigating what's different between your two clusters if this is working in one cluster but not the other. Alternatively, if you can provide a set of instructions...

I'll also add that stable-2.11.4 is the latest stable version, and you may want to try upgrading to see if that changes the behavior you're seeing.

Hi @AaronFriel! This is super interesting and a compelling use-case. It differs significantly from the way that the multicluster extension works today in that the current design expects clients to...

@Santosh1176 no problem, thanks for your interest! @pratikkumar-mohite this issue is still open and available to be worked on.