[READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. (grpc依赖)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
data-plane-api(CircleCI) f62e751a74 docs: remove not-implemented-hide for statsd sink prefix (#3358) 7 years ago
.circleci ci: remove docs/format jobs. (#619) 7 years ago
bazel grpc auth: support custom google grpc channel credentials (#3161) 7 years ago
ci ci: remove docs/format jobs. (#619) 7 years ago
diagrams
docs tap/fuzz: transport socket extension for traffic capture. (#3244) 7 years ago
envoy docs: remove not-implemented-hide for statsd sink prefix (#3358) 7 years ago
examples/service_envoy
test Protos for RBAC support. (#3133) 7 years ago
tools tap/fuzz: transport socket extension for traffic capture. (#3244) 7 years ago
.clang-format
.gitignore
API_OVERVIEW.md
BUILD
CONTRIBUTING.md api: trivial change to test data-plane-api mirroring. (#3086) 7 years ago
LICENSE
README.md api: some fixups post repo merge. (#3103) 7 years ago
STYLE.md
WORKSPACE
XDS_PROTOCOL.md

README.md

Data plane API

This tree hosts the configuration and APIs that drive Envoy. The APIs are also in some cases used by other proxy solutions that aim to interoperate with management systems and configuration generators that are built against this standard. Thus, we consider these a set of universal data plane APIs. See this blog post for more information on the universal data plane concept.

Repository structure

The API tree can be found at two locations:

Further API reading