package envoy.extensions.matching.common_inputs.transport_socket.v3

Get desktop application:
View/edit binary Protocol Buffers messages

Specifies that matching should be performed by the endpoint metadata. This input extracts metadata from the selected endpoint for transport socket selection. The metadata is extracted using a filter and path specification similar to :ref:`DynamicMetadataInput <envoy_v3_api_msg_extensions.matching.common_inputs.network.v3.DynamicMetadataInput>`. Example: Extract a metadata value for transport socket matching. .. code-block:: yaml typed_config: "@type": type.googleapis.com/envoy.extensions.matching.common_inputs.transport_socket.v3.EndpointMetadataInput filter: "envoy.transport_socket_match" path: - key: "socket_type" This configuration extracts the value at path ``["envoy.transport_socket_match"]["socket_type"]`` from the endpoint metadata for use in transport socket selection. [#extension: envoy.matching.inputs.endpoint_metadata]

• string filter = 1

  The filter name to retrieve the Struct from the endpoint metadata. If not specified, defaults to ``envoy.lb`` which is commonly used for load balancing metadata.

• repeated EndpointMetadataInput.PathSegment path = 2

  The path to retrieve the Value from the Struct.

Specifies the segment in a path to retrieve value from Metadata. Note: Currently it's not supported to retrieve a value from a list in Metadata. This means that if the segment key refers to a list, it has to be the last segment in a path.

Used in: EndpointMetadataInput

• oneof segment

  • string key = 1

    If specified, use the key to retrieve the value in a Struct.

Specifies that matching should be performed by filter state. This input extracts a value from filter state that was explicitly shared from the downstream connection to the upstream connection via ``TransportSocketOptions``. This enables flexible downstream-connection-based transport socket selection, such as matching on network namespace or any custom filter state data. Example: Match on network namespace stored in filter state. .. code-block:: yaml typed_config: "@type": type.googleapis.com/envoy.extensions.matching.common_inputs.transport_socket.v3.FilterStateInput key: "envoy.network.namespace" [#extension: envoy.matching.inputs.transport_socket_filter_state]

• string key = 1

  The key of the filter state object to retrieve. The object must implement serializeAsString() to be used for matching.

Specifies that matching should be performed by the locality metadata. This input extracts metadata from the endpoint's locality for transport socket selection. The metadata is extracted using a filter and path specification similar to :ref:`DynamicMetadataInput <envoy_v3_api_msg_extensions.matching.common_inputs.network.v3.DynamicMetadataInput>`. Example: Extract a metadata value from locality for transport socket matching. .. code-block:: yaml typed_config: "@type": type.googleapis.com/envoy.extensions.matching.common_inputs.transport_socket.v3.LocalityMetadataInput filter: "envoy.transport_socket_match" path: - key: "region" This configuration extracts the value at path ``["envoy.transport_socket_match"]["region"]`` from the locality metadata for use in transport socket selection. [#extension: envoy.matching.inputs.locality_metadata]

• string filter = 1

  The filter name to retrieve the Struct from the locality metadata. If not specified, defaults to ``envoy.lb`` which is commonly used for load balancing metadata.

• repeated LocalityMetadataInput.PathSegment path = 2

  The path to retrieve the Value from the Struct.

Specifies the segment in a path to retrieve value from Metadata. Note: Currently it's not supported to retrieve a value from a list in Metadata. This means that if the segment key refers to a list, it has to be the last segment in a path.

Used in: LocalityMetadataInput

• oneof segment

  • string key = 1

    If specified, use the key to retrieve the value in a Struct.

Configuration for the transport socket name action. This action sets the name of the transport socket to use when the matcher matches. [#extension: envoy.matching.action.transport_socket.name]

• string name = 1

  The name of the transport socket to use. This name must reference a named transport socket in the cluster's transport_socket_matches.