Alexander Yastrebov

@szuecs > 1. it leaks data from dataclient Well, routes themselves are a leak from dataclient then :) > 2. IMO IP address is enough and not explained well enough...

In Kubernetes endpoint metadata might also include pod name which, if logged along with endpoint IP, would simplify correlation with application and event logs that contain pod name.

I could not reproduce it. I've tried: ``` $ docker run --rm -it --network=host -m 4m registry.opensource.zalan.do/pathfinder/skipper:v0.11.144 skipper -access-log-disabled -inline-routes="r: * -> lua(\"function request(ctx,param) ctx.serve({status_code=301, header={location='https://example.org/a/path/' .. ctx.request.url}}) end\") ->...

Related #1868 enables incoming h2c connections

Hi, I get the idea of the change but struggle to understand the problem. Could you maybe provide an example of a configuration that you think is hard to manage...

https://github.com/zalando/skipper/pull/2054#issuecomment-1223784987 @xavivars Thank you for the explanation. Basically you want to have a weight associated with your custom predicate. One way would be to only fix `Weight(X)` accumulation and use...

:+1:

Connecting the dots. Filter cleanup is a part of route cleanup, so these #202 #1552 may be related

A related example of inconsistency is that [status](https://github.com/zalando/skipper/blob/master/docs/reference/filters.md#status) filter docs say > Sets the response status code to the given value, with no regards to the backend response. It is...

@szuecs True, probably status docs should be clarified