Skip to content

api: named filter config / filter config discovery service #7867

@mattklein123

Description

@mattklein123

I would like the ability to have individual filter configurations be named and fetchable from a discrete management server. This would allow federation of filter configuration from multiple sources, for example fault testing. Thought needs to be put into how this plays with FCDS for listener filters, draining, whether filters can swap config atomically via a new optional interface, etc.

If we do this right we should not need the TapDS IMO.

cc @envoyproxy/api-shepherds @htuch @yuval-k

Metadata

Metadata

Assignees

No one assigned

    Labels

    api/v3Major version release @ end of Q3 2019no stalebotDisables stalebot from closing an issue

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions