How source_cluster is propagated to upstream service

[s-krawczyk]

Description:
I try to use rate_limit with actions. Configured descriptor like below:

route: rate_limits: - actions: - source_cluster: {} -
That does not work. I am not getting any source_cluster. How this value flow from downstream service to upstream (destination) one? Is it a header? Does it even work? Any help or example would be helpful. Already sped 3 days on it. Reading source code etc. I would appreciate any direction. I want to use it for local rate limit.

Relevant Links:
>Any extra documentation required to understand the issue.
https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#config-route-v3-ratelimit-action

[htuch]

@wbpcode @mattklein123

Are you setting the same source cluster in the Envoy CLI and in the config? It's a little unclear from the OP.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.