mirror of https://github.com/hashicorp/consul
c1cb18c648
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.
|
||
|---|---|---|
| .. | ||
| clusters | ||
| endpoints | ||
| listeners | ||
| routes | ||
| test-leaf-cert.golden | ||
| test-leaf-key.golden | ||
| test-root-cert.golden | ||