Re: Filter name deprecations and dynamic metadata

[Stephan Zuercher]

+envoy-announce

On Thu, Feb 27, 2020 at 10:37 AM Stephan Zuercher <zuer...@gmail.com> wrote:

On Envoy master, HTTP filter[1] and network filter[2] names (among other extensions) have been changed to match the extension name. Old names continue to work, but trigger deprecation warnings in Envoy logs and increment the "runtime.deprecated_feature_use" metric. See the deprecation documentation for the current list updated names. The runtime feature "envoy.deprecated_features.allow_deprecated_extension_names" is enabled by default and may be disabled to proactively block use of the deprecated names.

Notably, HTTP and network filter sometimes generate dynamic metadata, consumed by other filters, using their filter name as a namespace. Filters whose canonical names have been updated will generate dynamic metadata using their new names so additional configuration may be necessary. Typically dynamic metadata is used for tracing, logging, and authentication. As noted in the documentation, the Mongo Proxy filter and Zookeeper filter are known to generate dynamic metadata.

[1] HTTP filter names changed at c5c1e5bb

[2] Network filter names changed at c0ab3a43

Stephan