envoyproxy/envoy

Per-XDS type callbacks

Open

#21,910 opened on Jun 27, 2022

View on GitHub
 (5 comments) (0 reactions) (0 assignees)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

Title: Add per-xds callback extensions that can run arbitrary code after an XDS response has been accepted.

Description: Currently, Envoy contains ClusterUpdateCallbacks which allows users to supply extensions that are run when clusters are added or removed. Similar functionality would be very useful for other XDS resources. This could be implemented either as a general XDS update hook, or on a per-resource basis.

Contributor guide

Research direction
Examine the existing ClusterUpdateCallbacks implementation to understand the pattern. Then design a generic interface for per XDS type callbacks that can be registered for different resource types.
Tech stack
cpp
Domain
backendnetworkinginfrastructure
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++EnvoyXDS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40