Update links to envoy docs on xDS protocol (#5871)

This commit is contained in:
Matt Keeler 2019-06-03 11:03:05 -05:00 committed by GitHub
parent a7c55ffed2
commit 923448f00e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 4 additions and 4 deletions

View File

@ -109,7 +109,7 @@ type ConfigManager interface {
// server is started. // server is started.
// //
// A full description of the XDS protocol can be found at // A full description of the XDS protocol can be found at
// https://github.com/envoyproxy/data-plane-api/blob/master/XDS_PROTOCOL.md // https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol
type Server struct { type Server struct {
Logger *log.Logger Logger *log.Logger
CfgMgr ConfigManager CfgMgr ConfigManager

View File

@ -196,7 +196,7 @@ func TestServer_StreamAggregatedResources_BasicProtocol(t *testing.T) {
// all the others (same version) but NACK the listener. This is the most // all the others (same version) but NACK the listener. This is the most
// subtle part of xDS and the server implementation so I'll elaborate. A full // subtle part of xDS and the server implementation so I'll elaborate. A full
// description of the protocol can be found at // description of the protocol can be found at
// https://github.com/envoyproxy/data-plane-api/blob/master/XDS_PROTOCOL.md. // https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol
// Envoy delays making a followup request for a type until after it has // Envoy delays making a followup request for a type until after it has
// processed and applied the last response. The next request then will include // processed and applied the last response. The next request then will include
// the nonce in the last response which acknowledges _receiving_ and handling // the nonce in the last response which acknowledges _receiving_ and handling

View File

@ -3,7 +3,7 @@
// Discovery Service (ADS) only as we control all config. // Discovery Service (ADS) only as we control all config.
// //
// A full description of the XDS protocol can be found at // A full description of the XDS protocol can be found at
// https://github.com/envoyproxy/data-plane-api/blob/master/XDS_PROTOCOL.md // https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol
// //
// xds.Server also support ext_authz network filter API to authorize incoming // xds.Server also support ext_authz network filter API to authorize incoming
// connections to Envoy. // connections to Envoy.

View File

@ -12,7 +12,7 @@ Consul Connect has first class support for using
[Envoy](https://www.envoyproxy.io) as a proxy. Consul configures Envoy by [Envoy](https://www.envoyproxy.io) as a proxy. Consul configures Envoy by
optionally exposing a gRPC service on the local agent that serves [Envoy's xDS optionally exposing a gRPC service on the local agent that serves [Envoy's xDS
configuration configuration
API](https://github.com/envoyproxy/data-plane-api/blob/master/XDS_PROTOCOL.md). API](https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol).
Consul can configure Envoy sidecars to proxy http/1.1, http2 or gRPC traffic at Consul can configure Envoy sidecars to proxy http/1.1, http2 or gRPC traffic at
L7 or any other tcp-based protocol at L4. Prior to Consul 1.5.0 Envoy proxies L7 or any other tcp-based protocol at L4. Prior to Consul 1.5.0 Envoy proxies