envoyproxy/envoy

xds: dynamic context params for new-style names

Open

#14,428 opened on Dec 15, 2020

View on GitHub
 (6 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/xdshelp wanted

Repository metrics

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

Description

This builds on the new xDS naming scheme described in #11264.

We have a need for the control plane to be able to provide some dynamic context parameters to be used when requesting LDS, RDS, CDS, EDS, et al resource names.

This doc describes the use-cases and proposes a mechanism to provide this functionality:

https://docs.google.com/document/d/1GO6HJ08wbMqLEjVGit5AxMiEAdHzZnT84f4A9Xg5Jp0/edit

Update: The above doc has been superseded by https://github.com/cncf/xds/blob/main/proposals/TP2-dynamically-generated-cacheable-xds-resources.md.

CC @htuch

Contributor guide

Research direction
Review the linked design doc and the proposal in cncf/xds repo; understand the new style naming scheme from issue #11264; explore how control plane parameters are currently passed and where dynamic context would be injected in LDS/RDS/CDS/EDS requests.
Tech stack
cpp
Domain
backendnetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
Mostly clear
Prerequisites
C++xDSEnvoy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15