feat(trafficdirector): update the api

#### trafficdirector:v3

The following keys were added:
- schemas.SocketAddress.properties.networkNamespaceFilepath.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/trafficdirector_v3.discovery.html

@@ -135,10 +135,11 @@ <h3>Method Details</h3>
           &quot;mode&quot;: 42, # The mode for the Pipe. Not applicable for abstract sockets.
           &quot;path&quot;: &quot;A String&quot;, # Unix Domain Socket path. On Linux, paths starting with &#x27;@&#x27; will use the abstract namespace. The starting &#x27;@&#x27; is replaced by a null byte by Envoy. Paths starting with &#x27;@&#x27; will result in an error in environments other than Linux.
         },
-        &quot;socketAddress&quot;: { # [#next-free-field: 7]
+        &quot;socketAddress&quot;: { # [#next-free-field: 8]
           &quot;address&quot;: &quot;A String&quot;, # The address for this socket. :ref:`Listeners ` will bind to the address. An empty address is not allowed. Specify ``0.0.0.0`` or ``::`` to bind to any address. [#comment:TODO(zuercher) reinstate when implemented: It is possible to distinguish a Listener address via the prefix/suffix matching in :ref:`FilterChainMatch `.] When used within an upstream :ref:`BindConfig `, the address controls the source address of outbound connections. For :ref:`clusters `, the cluster type determines whether the address must be an IP (``STATIC`` or ``EDS`` clusters) or a hostname resolved by DNS (``STRICT_DNS`` or ``LOGICAL_DNS`` clusters). Address resolution can be customized via :ref:`resolver_name `.
           &quot;ipv4Compat&quot;: True or False, # When binding to an IPv6 address above, this enables `IPv4 compatibility `_. Binding to ``::`` will allow both IPv4 and IPv6 connections, with peer IPv4 addresses mapped into IPv6 space as ``::FFFF:``.
           &quot;namedPort&quot;: &quot;A String&quot;, # This is only valid if :ref:`resolver_name ` is specified below and the named resolver is capable of named port resolution.
+          &quot;networkNamespaceFilepath&quot;: &quot;A String&quot;, # The Linux network namespace to bind the socket to. If this is set, Envoy will create the socket in the specified network namespace. Only supported on Linux. [#not-implemented-hide:]
           &quot;portValue&quot;: 42,
           &quot;protocol&quot;: &quot;A String&quot;,
           &quot;resolverName&quot;: &quot;A String&quot;, # The name of the custom resolver. This must have been registered with Envoy. If this is empty, a context dependent default applies. If the address is a concrete IP address, no resolution will occur. If address is a hostname this should be set for resolution other than DNS. Specifying a custom resolver with ``STRICT_DNS`` or ``LOGICAL_DNS`` will generate an error at runtime.
@@ -318,10 +319,11 @@ <h3>Method Details</h3>
               &quot;mode&quot;: 42, # The mode for the Pipe. Not applicable for abstract sockets.
               &quot;path&quot;: &quot;A String&quot;, # Unix Domain Socket path. On Linux, paths starting with &#x27;@&#x27; will use the abstract namespace. The starting &#x27;@&#x27; is replaced by a null byte by Envoy. Paths starting with &#x27;@&#x27; will result in an error in environments other than Linux.
             },
-            &quot;socketAddress&quot;: { # [#next-free-field: 7]
+            &quot;socketAddress&quot;: { # [#next-free-field: 8]
               &quot;address&quot;: &quot;A String&quot;, # The address for this socket. :ref:`Listeners ` will bind to the address. An empty address is not allowed. Specify ``0.0.0.0`` or ``::`` to bind to any address. [#comment:TODO(zuercher) reinstate when implemented: It is possible to distinguish a Listener address via the prefix/suffix matching in :ref:`FilterChainMatch `.] When used within an upstream :ref:`BindConfig `, the address controls the source address of outbound connections. For :ref:`clusters `, the cluster type determines whether the address must be an IP (``STATIC`` or ``EDS`` clusters) or a hostname resolved by DNS (``STRICT_DNS`` or ``LOGICAL_DNS`` clusters). Address resolution can be customized via :ref:`resolver_name `.
               &quot;ipv4Compat&quot;: True or False, # When binding to an IPv6 address above, this enables `IPv4 compatibility `_. Binding to ``::`` will allow both IPv4 and IPv6 connections, with peer IPv4 addresses mapped into IPv6 space as ``::FFFF:``.
               &quot;namedPort&quot;: &quot;A String&quot;, # This is only valid if :ref:`resolver_name ` is specified below and the named resolver is capable of named port resolution.
+              &quot;networkNamespaceFilepath&quot;: &quot;A String&quot;, # The Linux network namespace to bind the socket to. If this is set, Envoy will create the socket in the specified network namespace. Only supported on Linux. [#not-implemented-hide:]
               &quot;portValue&quot;: 42,
               &quot;protocol&quot;: &quot;A String&quot;,
               &quot;resolverName&quot;: &quot;A String&quot;, # The name of the custom resolver. This must have been registered with Envoy. If this is empty, a context dependent default applies. If the address is a concrete IP address, no resolution will occur. If address is a hostname this should be set for resolution other than DNS. Specifying a custom resolver with ``STRICT_DNS`` or ``LOGICAL_DNS`` will generate an error at runtime.

googleapiclient/discovery_cache/documents/trafficdirector.v3.json

@@ -128,7 +128,7 @@
 }
 }
 },
-"revision": "20250206",
+"revision": "20250423",
 "rootUrl": "https://trafficdirector.googleapis.com/",
 "schemas": {
 "Address": {
@@ -1102,7 +1102,7 @@
 "type": "object"
 },
 "SocketAddress": {
-"description": "[#next-free-field: 7]",
+"description": "[#next-free-field: 8]",
 "id": "SocketAddress",
 "properties": {
 "address": {
@@ -1117,6 +1117,10 @@
 "description": "This is only valid if :ref:`resolver_name ` is specified below and the named resolver is capable of named port resolution.",
 "type": "string"
 },
+"networkNamespaceFilepath": {
+"description": "The Linux network namespace to bind the socket to. If this is set, Envoy will create the socket in the specified network namespace. Only supported on Linux. [#not-implemented-hide:]",
+"type": "string"
+},
 "portValue": {
 "format": "uint32",
 "type": "integer"