envoyproxy/envoy

Expose extensions in the ConfigDump endpoint.

Open

#9,097 opened on Nov 21, 2019

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
enhancementhelp wanted

Repository metrics

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

Description

Title:

Expose extensions in the ConfigDump endpoint.

Description:

The set of extensions in the envoy binary are logged at startup, but not otherwise exposed. If these extensions were exposed by the config_dump endpoint, then it would be easier for operational tooling (e.g facter) to track what extensions are available. Another use that I have in mind for this is to let Kubernetes ingress controllers inspect an envoy process to ensure that the features it needs are compiled in.

Contributor guide

Research direction
Study the config dump endpoint implementation in Envoy and how extensions are registered. Investigate the extension registration mechanism and prototype a way to serialize the list of compiled in extensions into the admin output.
Tech stack
cpp
Domain
backendapidevops
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.
1-2 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++Envoy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40