diff --git a/BUILD b/BUILD index 7a6671dd..d8782fb9 100644 --- a/BUILD +++ b/BUILD @@ -133,18 +133,12 @@ proto_library( "//envoy/config/common/matcher/v3:pkg", "//envoy/config/core/v3:pkg", "//envoy/config/endpoint/v3:pkg", - "//envoy/config/filter/thrift/router/v2alpha1:pkg", "//envoy/config/grpc_credential/v3:pkg", - "//envoy/config/health_checker/redis/v2:pkg", "//envoy/config/listener/v3:pkg", "//envoy/config/metrics/v3:pkg", "//envoy/config/overload/v3:pkg", "//envoy/config/ratelimit/v3:pkg", "//envoy/config/rbac/v3:pkg", - "//envoy/config/resource_monitor/fixed_heap/v2alpha:pkg", - "//envoy/config/resource_monitor/injected_resource/v2alpha:pkg", - "//envoy/config/retry/omit_canary_hosts/v2:pkg", - "//envoy/config/retry/previous_hosts/v2:pkg", "//envoy/config/route/v3:pkg", "//envoy/config/tap/v3:pkg", "//envoy/config/trace/v3:pkg", diff --git a/xds_protocol.rst b/xds_protocol.rst index edd12f6b..71c5f646 100644 --- a/xds_protocol.rst +++ b/xds_protocol.rst @@ -772,12 +772,12 @@ Later the xDS client spontaneously requests the "wc" resource. On reconnect the Incremental xDS client may tell the server of its known resources to avoid resending them over the network by sending them in -:ref:`initial_resource_versions `. +:ref:`initial_resource_versions `. Because no state is assumed to be preserved from the previous stream, the reconnecting client must provide the server with all resource names it is interested in. Note that for wildcard requests (CDS/LDS/SRDS), the request must have no resources in both -:ref:`resource_names_subscribe ` and -:ref:`resource_names_unsubscribe `. +:ref:`resource_names_subscribe ` and +:ref:`resource_names_unsubscribe `. .. figure:: diagrams/incremental-reconnect.svg :alt: Incremental reconnect example