Guy Daich

@kcbabo - was this also implemented for EE charts?

Thanks @kcbabo. Can this be ported to 1.11 ?

Hi @kcbabo . I think that we maybe had a small miscommunication here. https://github.com/solo-io/gloo/pull/6761 created a dedicated value for digests. Prior to this change, it was already possible to specify...

> How important is it to deploy gloo fed using the canary pattern? Gloo Fed is a privileged component that controls configuration for multiple edge control planes. I think that...

> Can limit the scope to having Gloo Fed backwards compatible with GE. Right. For example, the Gloo Mesh Control Plane is [compatible with n-1 version relay agents](https://docs.solo.io/gloo-mesh-enterprise/main/reference/version/versions/#version-skew-policy-for-management-and-remote-clusters) to support...

It seems that the gateway-api consensus is to not represent HTTP3 as a distinct protocol: https://github.com/kubernetes-sigs/gateway-api/issues/687. Istio’s experimental support for HTTP3 is also aligned with this state: https://github.com/istio/istio/wiki/Experimental-QUIC-and-HTTP-3-support-in-Istio-gateways. Considering these...

@zirain - do you propose to use ECDS because you want EG's XDS server to delegate configuration for such extension to a different (extension owner/vendor) XDS server? While this provides...

Please assign to me.

@kflynn mentioned this GEP: https://gateway-api.sigs.k8s.io/geps/gep-1867 in a different discussion. @liorokman - do you think that GW parameters can be used here as an alternative (acting like HTTPRoute filters) ?

+1 in general. @aoledk - can you maybe describe the scenario where this is needed?