mirror of https://github.com/hashicorp/consul
a7803bd829
* xds: Ensure v2 route match is populated for gRPC Similar to HTTP, ensure that route match config (which is required by Envoy) is populated when default values are used. Because the default matches generated for gRPC contain a single empty `GRPCRouteMatch`, and that proto does not directly support prefix-based config, an interpretation of the empty struct is needed to generate the same output that the `HTTPRouteMatch` is explicitly configured to provide in internal/mesh/internal/controllers/routes/generate.go. * xds: Ensure protocol set for gRPC resources Add explicit protocol in `ProxyStateTemplate` builders and validate it is always set on clusters. This ensures that HTTP filters and `http2_protocol_options` are populated in all the necessary places for gRPC traffic and prevents future unintended omissions of non-TCP protocols. Co-authored-by: John Murret <john.murret@hashicorp.com> --------- Co-authored-by: John Murret <john.murret@hashicorp.com> |
||
|---|---|---|
| .. | ||
| l4-implicit-and-explicit-destinations-tproxy.golden | ||
| l4-multi-destination.golden | ||
| l4-multiple-implicit-destinations-tproxy.golden | ||
| l4-single-destination-ip-port-bind-address.golden | ||
| l4-single-destination-unix-socket-bind-address.golden | ||
| l4-single-implicit-destination-tproxy.golden | ||
| mixed-multi-destination.golden | ||
| multiport-l4-and-l7-multiple-implicit-destinations-tproxy.golden | ||
| multiport-l4-and-l7-single-implicit-destination-tproxy.golden | ||
| multiport-l4-and-l7-single-implicit-destination-with-multiple-workloads-tproxy.golden | ||