package envoy.extensions.filters.network.generic_proxy.v3

Get desktop application:
View/edit binary Protocol Buffers messages

[#next-free-field: 8]

• string stat_prefix = 1

  The human readable prefix to use when emitting statistics.

• optional config.core.v3.TypedExtensionConfig codec_config = 2

  The codec which encodes and decodes the application protocol. [#extension-category: envoy.generic_proxy.codecs]

• oneof route_specifier

  • GenericRds generic_rds = 3

    The generic proxies route table will be dynamically loaded via the meta RDS API.

  • RouteConfiguration route_config = 4

    The route table for the generic proxy is static and is specified in this property.

• repeated config.core.v3.TypedExtensionConfig filters = 5

  A list of individual Layer-7 filters that make up the filter chain for requests made to the proxy. Order matters as the filters are processed sequentially as request events happen. [#extension-category: envoy.generic_proxy.filters]

• optional http_connection_manager.v3.HttpConnectionManager.Tracing tracing = 6

  Tracing configuration for the generic proxy.

• repeated config.accesslog.v3.AccessLog access_log = 7

  Configuration for :ref:`access logs <arch_overview_access_logs>` emitted by generic proxy.

Used in: GenericProxy

• optional config.core.v3.ConfigSource config_source = 1

  Configuration source specifier for RDS.

• string route_config_name = 2

  The name of the route configuration. This name will be passed to the RDS API. This allows an Envoy configuration with multiple generic proxies to use different route configurations.

The generic proxy makes use of the xDS matching API for routing configurations. In the below example, we combine a top level tree matcher with a linear matcher to match the incoming requests, and send the matching requests to v1 of the upstream service. .. code-block:: yaml name: example routes: matcher_tree: input: name: request-service typed_config: "@type": type.googleapis.com/envoy.extensions.filters.network.generic_proxy.matcher.v3.ServiceMatchInput exact_match_map: map: service_name_0: matcher: matcher_list: matchers: - predicate: and_matcher: predicate: - single_predicate: input: name: request-properties typed_config: "@type": type.googleapis.com/envoy.extensions.filters.network.generic_proxy.matcher.v3.PropertyMatchInput property_name: version value_match: exact: v1 - single_predicate: input: name: request-properties typed_config: "@type": type.googleapis.com/envoy.extensions.filters.network.generic_proxy.matcher.v3.PropertyMatchInput property_name: user value_match: exact: john on_match: action: name: route typed_config: "@type": type.googleapis.com/envoy.extensions.filters.network.generic_proxy.action.v3.routeAction cluster: cluster_0

Used in: GenericProxy

• string name = 1

  The name of the route configuration. For example, it might match route_config_name in envoy.extensions.filters.network.generic_proxy.v3.Rds.

• optional xds.type.matcher.v3.Matcher routes = 2

  The match tree to use when resolving route actions for incoming requests. If no any virtual host is configured in the ``virtual_hosts`` field or no special wildcard virtual host is configured, the ``routes`` field will be used as the default route table. If both the wildcard virtual host and ``routes`` are configured, the configuration will fail to load.

• repeated VirtualHost virtual_hosts = 3

  An array of virtual hosts that make up the route table.

Used in: RouteConfiguration

• string name = 1

  The name of the virtual host.

• repeated string hosts = 2

  A list of hosts that will be matched to this virtual host. Wildcard hosts are supported in the suffix or prefix form. Host search order: 1. Exact names: ``www.foo.com``. 2. Suffix wildcards: ``*.foo.com`` or ``*-bar.foo.com``. 3. Prefix wildcards: ``foo.*`` or ``foo-*``. 4. Special wildcard ``*`` matching any host and will be the default virtual host. .. note:: The wildcard will not match the empty string. e.g. ``*-bar.foo.com`` will match ``baz-bar.foo.com`` but not ``-bar.foo.com``. The longest wildcards match first. Only a single virtual host in the entire route configuration can match on ``*``. A domain must be unique across all virtual hosts or the config will fail to load.

• optional xds.type.matcher.v3.Matcher routes = 3

  The match tree to use when resolving route actions for incoming requests.