42224fe45c
If a proxied service is a gRPC or HTTP2 service, but a path is exposed
using the HTTP1 or TCP protocol, Envoy should not be configured with
`http2ProtocolOptions` for the cluster backing the path.
A situation where this comes up is a gRPC service whose healthcheck or
metrics route (e.g. for Prometheus) is an HTTP1 service running on
a different port. Previously, if these were exposed either using
`Expose: { Checks: true }` or `Expose: { Paths: ... }`, Envoy would
still be configured to communicate with the path over HTTP2, which would
not work properly.
|
||
|---|---|---|
| .. | ||
| testdata | ||
| clusters.go | ||
| clusters_test.go | ||
| config.go | ||
| config_test.go | ||
| endpoints.go | ||
| endpoints_test.go | ||
| failover_math.go | ||
| failover_math_test.go | ||
| golden_test.go | ||
| listeners.go | ||
| listeners_test.go | ||
| naming.go | ||
| response.go | ||
| routes.go | ||
| routes_test.go | ||
| server.go | ||
| server_oss.go | ||
| server_test.go | ||
| testing.go | ||
| xds.go | ||