More precise and intuitive filter_chains addressing

[isniukArte]

I use Envoy Gateway in k8s with dynamic configuration. And while dynamic configuration by itself is an advantage, it creates some obstacles in adding HTTP filters.

For example, I want to add MaxMind geoip filter. As I understand, EnvoyPatchPolicy is the only way to do that in a native way (w/o WASM). I want to run it for every domain. But I see no way for this. Spreading over a random large number makes the policy invalid. Default chain, as I understand, is a fallback chain and not the one applied for every domain.

Another problem appears when you try to add something for a specific domain. Let's say now I want to add RBAC filter for specific domains. Am I relying only on the index number of filter chains here? What if I add a few more domains simultaneously? Do I need to recheck the config dump to find the index number? What if one of the domains were removed? Will it change the order in the array?

I feel like I'm missing something here. Maybe another way to add HTTP filters or a more convenient way to address specific filter_chains. Because, as I understand, they are the cornerstone of additional features that native k8s couldn't provide. And in the current state, they seem to be counterintuitive and fault-prone.

Thanks in advance for any advice.

[isniukArte]

While it wasn't possible to wildcard by the path, there is a way to use JSONPath instead of path. Path isn't required.
Hence, it is possible to createa wildcard policy:
filter_chains[*].filters[0].typed_config.http_filters[0]
and policy targetting specific domain:
filter_chains[?(@.filter_chain_match.server_names[*]=='mydomain.com')].filters[0].typed_config.http_filters[0]