Guy Daich
Guy Daich
cc @AliceProxy
> By default seems to make more sense here. > > Opt in would cause a lot of confusion for users like this issue. Also, ext auth service is a...
> if we are finally going down the path of supporting non k8s backend types, I'd suggest for us to also consider a generic way to represent a address (e.g....
It would be nice to have cross-namespace support and reference-grant opt-out options for: - Policy BackendRefs - Policy TargetRefs Maybe also: - xRoutes BackendRefs
In the last community meeting, the option to use weighted clusters ~~(clusters within clusters)~~ was raised as a means of translating "cluster" settings derived from attributes found in backendRef.
cc @arkodg Looking at the envoy config, it seems that weighted clusters are a route feature: https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto.html#config-route-v3-weightedcluster. I misunderstood it to be a cluster feature. For example, here: https://github.com/envoyproxy/gateway/blob/9eff541254221963dcacadb02e18b6ac7cb53c73/internal/xds/translator/testdata/out/xds-ir/http-route-weighted-backend-with-filters.routes.yaml#L31 So,...
Notes from last community meeting: - Weighted Cluster will indeed not work here - Prefer to avoid breaking and complicating the yaml API - Prefer to align with the GW-API...
relates to #2924
> if we add into field into non xRoute backendRefs, we may need to pluralize existing instantiations to `backendRefs` Yes, also ext-proc. I don't object, and this is in-line with...