api: deprecate the node.listening_addresses field (#12691)

This was added for gRPC server support, but we've decided to use resource names instead to explicitly request the listeners we want by name. This is more in-line with the new naming scheme described in the "xDS Transport Next Steps" design. Signed-off-by: Mark D. Roth <[email protected]>
envoyproxy · Aug 17, 2020 · 05cbb30 · 05cbb30
1 parent 0f89615
commit 05cbb30
Show file tree

Hide file tree

Showing 40 changed files with 1,601 additions and 44 deletions.
diff --git a/api/envoy/admin/v4alpha/config_dump.proto b/api/envoy/admin/v4alpha/config_dump.proto
diff --git a/api/envoy/config/core/v3/base.proto b/api/envoy/config/core/v3/base.proto
@@ -196,7 +196,7 @@ message Node {
   // for filtering :ref:`listeners <config_listeners>` to be returned. For example,
   // if there is a listener bound to port 80, the list can optionally contain the
   // SocketAddress `(0.0.0.0,80)`. The field is optional and just a hint.
-  repeated Address listening_addresses = 11;
+  repeated Address listening_addresses = 11 [deprecated = true];
 }
 
 // Metadata provides additional inputs to filters based on matched listeners,

diff --git a/api/envoy/config/core/v4alpha/base.proto b/api/envoy/config/core/v4alpha/base.proto
diff --git a/api/envoy/config/metrics/v4alpha/metrics_service.proto b/api/envoy/config/metrics/v4alpha/metrics_service.proto
diff --git a/api/envoy/config/route/v4alpha/scoped_route.proto b/api/envoy/config/route/v4alpha/scoped_route.proto
diff --git a/api/envoy/service/accesslog/v4alpha/BUILD b/api/envoy/service/accesslog/v4alpha/BUILD
diff --git a/api/envoy/service/accesslog/v4alpha/als.proto b/api/envoy/service/accesslog/v4alpha/als.proto
diff --git a/api/envoy/service/discovery/v4alpha/BUILD b/api/envoy/service/discovery/v4alpha/BUILD
diff --git a/api/envoy/service/discovery/v4alpha/ads.proto b/api/envoy/service/discovery/v4alpha/ads.proto