envoyproxy/envoy

Asynchronous custom resolvers

Open

#10,361 opened on Mar 12, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/dnsarea/listenerarea/load balancingenhancementhelp wantedtech debt

Repository metrics

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

Description

https://github.com/envoyproxy/envoy/issues/1477 added custom resolvers for address messages, but with a synchronous resolution limitation. This rules out the use of RPCs or DNS for address resolution. This issue tracks bringing async customer resolver capabilities to Envoy.

Contributor guide

Research direction
Study the existing synchronous custom resolver implementation in Envoy (from issue #1477) and design an asynchronous extension point that allows RPC or DNS based resolution. Look into Envoy's async infrastructure and thread model to ensure no blocking calls.
Tech stack
cpp
Domain
backendinfrastructure
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.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20