Custom hash key for maglev lb

[BorshchevY]

Hi guys!
We are on the way to replace Envoy Proxy with static configuration with Envoy Gateway in our k8s cluster.
But we need to deal with customization of the hash key for upstreams for maglev lb.
With static config we used a config like mentioned here - https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/load_balancers#maglev
` filter_metadata:

envoy.lb:

  hash_key: "YOUR HASH KEY"

`
Is this a way to do something like this with Envoy Gateway API concept?
Our goal to have a consistent routing to the statefulset application instances while hashing upstream instances not by ip-addresses but by the custom key (hostname, for example).

[arkodg]

hey this is supported as a first class API field
https://gateway.envoyproxy.io/docs/tasks/traffic/load-balancing/#consistent-hash

[BorshchevY]

I suppose we are talking about slightly different things.
If I understood clearly the maglev uses ip-address of the upstream host while build table, but I want to force Envoy to use hostname as hash key for building maglev table.

[arkodg]

header support is available

    type: ConsistentHash
    consistentHash:
      type: Header
      header: "...."

https://gateway.envoyproxy.io/docs/api/extension_types/#consistenthash

[BorshchevY]

If I understand correctly, this is about the options for hashing user requests. What I need to change is the method by which the upstream servers will be hashed when constructing the Maglev table.