Description:

Describe the desired behavior, what scenario it enables and how it
would be used.

Chash on multiple headers is a legit use case. Example: when user identity is split across multiple headers, X-Tenant-ID + X-User-ID in multi-tenant apps.

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Hash_policy is a list in envoy https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto, so we could support this in gateway

opened on behalf of Owen from envoy gateway slack channel.

https://envoyproxy.slack.com/archives/C03E6NHLESV/p1760003411597089