per cluster HTTP filter config about envoy HOT 5 OPEN

cc @mattklein123

cc @zhaohuabing for suggestion from envoy-gateway
cc @kyessenov for suggestion from istio

from envoy.

While per-cluster filter could be valuable, per-route filter seems sufficient for EG's current need. I'm not aware of any requirements for per-cluster filter in EG.

@wbpcode Could you provide some concrete examples of use cases where per-cluster would be essential? This would help others evaluate the necessity of this feature.

from envoy.

From Istio, service doesn't correspond to an upstream cluster. From a general perspective, "upstream cluster" configs are notoriously low-level and don't map well to service ownership (e.g. VIP or domain name).

from envoy.

From Istio, service doesn't correspond to an upstream cluster. From a general perspective, "upstream cluster" configs are notoriously low-level and don't map well to service ownership (e.g. VIP or domain name).

Get it. I agree mesh needn't that. Esp considering that in most cases, the VH could be treat an abstraction of service (VIP, K8S server, domain...) in the mesh.

from envoy.

While per-cluster filter could be valuable, per-route filter seems sufficient for EG's current need. I'm not aware of any requirements for per-cluster filter in EG.

@wbpcode Could you provide some concrete examples of use cases where per-cluster would be essential? This would help others evaluate the necessity of this feature.

In our scenarios, we may want to use specific filter config for specific backend service. In the gateway scenario, the VH or routes cannot be mapped one-to-one to a backend service.
So, I am looking a new way to support the per-service-filter-config. Although in fact, the cluster couldn't be mapped one-to-one to a backend service. But I don't find a better way. orz.

Anyway, if the community is no interested in this, I will pend it up. :)

from envoy.