envoyproxy / envoyproxy/envoy

filter chain match extensibility

Open
#18,685 6 comments 0 reactions 0 assignees View on GitHub
area/listener area/metadata help wanted
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
437

Description

Filter chain matching algorithm is fairly rigid and has some flaws (e.g. the fixed ordering requires duplication of chains causing complexity in xDS code). It is also not extensible since it forces the use of real stream properties (like destination IP).

The proposal is to add a match condition based on dynamic metadata. We also propose to make metadata match first priority before destination port match so that it can be added incrementally. If a listener chooses to use metadata matching, that would take effect by overriding existing matching.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.