Wasm

Attention

The Wasm filter is experimental and is currently under active development. Capabilities will be expanded over time and the configuration structures are likely to change.

The HTTP Wasm filter is used to implement an HTTP filter with a Wasm plugin.

Note

This filter is not supported on Windows.

Example configuration

Example filter configuration:

wasm envoy.yaml
24                  cluster: web_service
25
26          http_filters:
27          - name: envoy.filters.http.wasm
28            typed_config:
29              "@type": type.googleapis.com/envoy.extensions.filters.http.wasm.v3.Wasm
30              config:
31                name: "my_plugin"
32                root_id: "my_root_id"
33                # if your wasm filter requires custom configuration you can add
34                # as follows
35                configuration:
36                  "@type": "type.googleapis.com/google.protobuf.StringValue"
37                  value: |
38                    {}
39                vm_config:
40                  runtime: "envoy.wasm.runtime.v8"
41                  vm_id: "my_vm_id"
42                  code:
43                    local:
44                      filename: "lib/envoy_filter_http_wasm_example.wasm"
45          - name: envoy.filters.http.router
46            typed_config:
47              "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
48
49  clusters:

The preceding snippet configures a filter from a Wasm binary on local disk.