listener: release multiple addresses listener (#22097)

Signed-off-by: He Jie Xu <[email protected]>

api/envoy/admin/v3/listeners.proto

@@ -37,6 +37,5 @@ message ListenerStatus {
 
   // The additional addresses the listener is listening on as specified via the :ref:`additional_addresses <envoy_v3_api_field_config.listener.v3.Listener.additional_addresses>`
   // configuration.
-  // [#not-implemented-hide:]
   repeated config.core.v3.Address additional_local_addresses = 3;
 }

api/envoy/config/listener/v3/listener.proto

@@ -34,7 +34,6 @@ option (udpa.annotations.file_status).package_version_status = ACTIVE;
 // Listener :ref:`configuration overview <config_listeners>`
 
 // The additional address the listener is listening on.
-// [#not-implemented-hide:]
 message AdditionalAddress {
   core.v3.Address address = 1;
 }
@@ -124,7 +123,6 @@ message Listener {
   // The additional addresses the listener should listen on. The addresses must be unique across all
   // listeners. Multiple addresses with port 0 can be supplied. When using multiple addresses in a single listener,
   // all addresses use the same protocol, and multiple internal addresses are not supported.
-  // [#not-implemented-hide:]
   repeated AdditionalAddress additional_addresses = 33;
 
   // Optional prefix to use on listener stats. If empty, the stats will be rooted at

changelogs/current.yaml

@@ -13,5 +13,8 @@ removed_config_or_runtime:
 # *Normally occurs at the end of the* :ref:`deprecation period <deprecated>`
 
 new_features:
+- area: listener
+  change: |
+    added multiple listening addresses in single listener. :ref:`listener additional addresses<envoy_v3_api_field_config.listener.v3.Listener.additional_addresses>`.
 
 deprecated: