David McLaughlin

@danny-devops That sounds like a separate issue to anything mentioned here given you are seeing OOM kills and are not using 2.13.x. Do you mind creating a new ticket so...

Sorry for the delay in responding - this sounds reasonable and we would welcome a PR here!

Thanks for reporting this. I agree this is a problem as it increases costs. We cannot change the request back to a value that does not match limits without having...

Can you share configuration that helps us reproduce this? Do you have metrics for Service A when they get into this state? You can get these by running `linkerd diagnostics...

Thanks for the additional context. Some clarifying questions: * Do you mean that the aggregator keeps sending the requests to service 1? From your diagram the aggregator doesn't talk directly...

Thanks for reporting this - we are unlikely to have bandwidth to look at this before the new year. But if anyone wants to try and submit a fix we'd...

Can you provide a kubectl describe of the control plane pod? The opaque ports issue you mentioned that was fixed in 2.14.3 did not manifest as OOM kills, so you...

A couple of clarifying questions: * Did you unsafely restart the node (i.e. turn the power switch off) or did you gracefully terminate it and drain the workloads? * Once...

Thanks for the kind words @4FunAndProfit ! For 2.17 scope we are adding inbound rate-limiting only that is focused on the user story in the issue (helping service owners protect...