deusxanima

@iamhritik , 2.12.2 is out and you should be able to test and confirm the fix.

@olix0r spent some time testing various scenarios today and was able to confirm that setting `skip-inbound-ports` and `skip-outbound-ports` annotations on the workload does not preserve the original source-ip in the...

For anyone following along, the recommended way to get around the issue of `x-forwarded-for` and `forwarded` headers being changed is to set the `config.linkerd.io/skip-inbound-ports` annotation on the ingress/proxy deployment. For...

@mateiidavid , got clarification that the user seeing this in EKS was seeing a separate issue so I've edited original description to only cover AKS. I've made note of the...

Encountered this issue again while troubleshooting a few multicluster gateway liveness issues which made it very difficult to separate the noise out from the actual errors and required back-and-forth with...

@elstevega You'll have to update the file you're running the main scripts in to include the additional parameter. UnusualPi's fix added an additional parameter that gets passed in and which...

Confirmed that when users encountered the issue documented above, they were setting the promURL via Helm (not linkerd CLI)

Hi @tehlers320 , Our team is looking into this and we'll have an update for you today with our analysis and/or next steps.

> Hi @deusxanima, would this PR address #3760? It's one of our oldest docs issues, so it'd be great to see it cleared! Partially, yes. Specifically it would cover the...