You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Andy Lindeman c1cb18c648 proxycfg: support path exposed with non-HTTP2 protocol (#7510) ... 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.		5 years ago
..
clusters	proxycfg: support path exposed with non-HTTP2 protocol (#7510)	5 years ago
endpoints	wan federation via mesh gateways (#6884)	5 years ago
listeners	wan federation via mesh gateways (#6884)	5 years ago
routes	Fixes envoy config when both RetryOn* values are set (#7280)	5 years ago
test-leaf-cert.golden	…
test-leaf-key.golden	…
test-root-cert.golden	…