Sotiris Nanopoulos

@geomacy will take a look later today.

speaking of which another thing I realized is that `grpc-go` (and maybe other implementations) put the `ORCA` headers in the `trailers` so an operator would need to remove both the...

> yes; I believe that gRPC will put the ORCA metrics in trailers generally. and the response_headers_to_remove only removes response headers, not response trailers. Also I cant seem to find...

>yurp, that API doesn't exist today. would be a welcome addition if you'd like to open a PR? Yeah for sure, Let me summarize bellow the full recommendation ### Problem...

> One concern with removal of endpoint-load-metrics headers/trailers is that this will make it more difficult to observe / debug ORCA reports as downstream filters as well as clients will...

> On the response path the router filter goes first: Yeah in that case the above makes sense

If it helps with the decision making I think the current default of propagating makes sense due to the docs here https://www.envoyproxy.io/docs/envoy/latest/configuration/best_practices/edge#best-practices-edge >Envoy is a production-ready edge proxy, however, the...

After doing a bit of research and playing around with the existing `API` I validated that: ``` - name: downstream-header-mutation typed_config: "@type": type.googleapis.com/envoy.extensions.filters.http.header_mutation.v3.HeaderMutation mutations: response_mutations: - remove: "trailer-key" ``` does...

Linking this here as well https://github.com/envoyproxy/envoy/pull/39433 since I assume folks are interested. It is marked as draft because I wanted the CI to be green, but I have tested it...

The mutation `PR` was merged yesterday, wanted to do some `doc` changes on top of it to explain to users about the edge case and then we can close the...