Dynamic Modules Upstream HTTP TCP Bridge (proto)

extensions.upstreams.http.dynamic_modules.v3.Config

[extensions.upstreams.http.dynamic_modules.v3.Config proto]

Configuration for the dynamic modules upstream HTTP TCP bridge.

This upstream type delegates HTTP-to-TCP protocol bridging to a dynamic module. The module transforms HTTP request headers and body into raw TCP data for the upstream connection, and converts raw TCP response data back into HTTP responses for the downstream client.

This extension has the qualified name envoy.upstreams.http.dynamic_modules

Note

This extension is functional but has not had substantial production burn time, use only with this caveat.

This extension is not hardened and should only be used in deployments where both the downstream and upstream are trusted.

Tip

This extension extends and can be used with the following extension category:

envoy.upstreams

{
  "dynamic_module_config": {...},
  "bridge_name": ...,
  "bridge_config": {...}
}

dynamic_module_config: (extensions.dynamic_modules.v3.DynamicModuleConfig, REQUIRED) The dynamic module configuration.

bridge_name: (string, REQUIRED) The name to identify the bridge implementation within the module. This is passed to the module’s envoy_dynamic_module_on_upstream_http_tcp_bridge_config_new function.

bridge_config: (Any) The configuration for the module’s bridge implementation. This is passed to the module’s envoy_dynamic_module_on_upstream_http_tcp_bridge_config_new function. The configuration can be any protobuf message. However, it is recommended to use google.protobuf.Struct, google.protobuf.StringValue, or google.protobuf.BytesValue. These types are passed directly as bytes to the module, so the module does not need to have knowledge of protobuf encoding. Otherwise, the serialized bytes of the type are passed. If not specified, an empty configuration is passed.