envoyproxy/envoy

FilterChain Discovery Service (FDS)

Open

#4,540 opened on Sep 26, 2018

View on GitHub
 (47 comments) (18 reactions) (1 assignee)C++ (5,373 forks)batch import
api/v3design proposalhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

In order to support filter chain updates without forcing a full listener drain, it's been suggested we add a FilterChain Discovery Service. This would allow individual FilterChains belonging to a Listener to be independently discovered and updated.

This would also lend support to finer grained Listener resource naming for incremental and on-demand xDS (generalizing https://github.com/envoyproxy/envoy/issues/2500).

Opening this issue to track any design work and ownership.

@ggreenway @andraxylia @lizan @PiotrSikora @mattklein123

Contributor guide

Research direction
Study Envoy's filter chain architecture and the existing xDS protocol to understand how a FilterChain Discovery Service could be implemented. Look at related issues and design documents.
Tech stack
cpp
Domain
apibackendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
C++EnvoyxDS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30