envoyproxy/envoy

Downstream TLS at listener level

Open

#25,787 opened on Feb 26, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/listenerhelp wantedquestion

Repository metrics

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

Description

Is it currently possible to apply DownstreamTLS context for any new connection opened on a specific TCP listener, instead of a filter chain? My motivation for this is so I could match a filter chain by L7 information, rather than only relying on information that is available before TLS handshake is made. Http inspector for example can only help matching a filter chain if there's no TLS in the context. Thanks

Contributor guide

Research direction
Investigate the current implementation of DownstreamTLS context in Envoy's listener and filter chain, and propose changes to allow listener level TLS context application.
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.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Clear
Prerequisites
C++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65