envoyproxy/envoy

xDS conformance test suite

Open

#11,299 opened on May 22, 2020

View on GitHub
 (11 comments) (2 reactions) (0 assignees)C++ (27,997 stars) (5,373 forks)batch import
api/v3help wanted

Description

It would be helpful to control plane implementors and client implementations to have an xDS conformance test suite that is independent of Envoy. I think this would largely look like some scripts (Python or Go) that create xDS gRPC connections and exercise some xDS exchanges.

A priority area here is delta xDS, which control plane implementors consider to be challenging to verify.

I think we could separate this work into two parts; building out the basic test infra and then building out an increasingly more complete test suite.

@snowp @howardjohn @derekargueta

Contributor guide

Tech stack
gopythongrpc
Domain
testingbackendinfrastructure
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.
over 1 week
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
xDS protocolgRPCGo or Python scriptingEnvoy control plane concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Start by reviewing the xDS specification and existing Envoy test infrastructure. Look into the issue comments for direction from @snowp, @howardjohn, and @derekargueta. The work is split into basic test infrastructure (likely in Go or Python with gRPC) and then building out a comprehensive test suite. Focus on delta xDS as a priority. Explore existing conformance tests in other projects for patterns.