Arko Dasgupta

hey @shawnh2 when we write docs, we should probably highlight that standalone mode is still experimental and not meant for production yet, and not all features work out of the...

we've fail closed by default for all Policy APIs, should we do the same for extension manager (if unable to connect or unable to get a response in time )...

> Maybe add a configuration flag in the extension manager configuration section to specify if the extension manager should fail-open or fail-close? yeah thats a good home to add the...

isnt this already supported https://gateway.envoyproxy.io/docs/tasks/traffic/client-traffic-policy/#configure-downstream-per-connection-buffer-limit ? cc @yaelSchechter

maps to https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#custom-max-body-size in ingress-nginx

thanks for brainstorming on the location ! CTP vs BTP, adding some more questions to help us narrow down on the location @markwinter @luvk1412 hoping you can help answer these...

thanks @markwinter @luvk1412 , let's continue with BTP then

keeping this open to track docs work

@nezdolik i'm curious why this is happening, im trying to better understand the collision can you share a snippet of the config dump especially the portion of the RateLimit filter...

okay found the problem, the ratelimit runner is treating every subscribed message as SoTW https://github.com/envoyproxy/gateway/blob/d784c3237765aa258c3526b32765dd9c3abf6415/internal/globalratelimit/runner/runner.go#L124 but the publisher / gateway-api runner is sending individual messages per gatewayclass https://github.com/envoyproxy/gateway/blob/d784c3237765aa258c3526b32765dd9c3abf6415/internal/gatewayapi/runner/runner.go#L81