[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) 5281bb74e2 admin: add json serialized proto for /clusters (#3478) 7 years ago
.circleci
bazel config_dump: bump protobuf/PGV versions to fix round-trip proto conversion bugs. (#3697) 7 years ago
ci
diagrams
docs admin: add json serialized proto for /clusters (#3478) 7 years ago
envoy admin: add json serialized proto for /clusters (#3478) 7 years ago
examples/service_envoy
test Header to metadata filter (#2436) (#3633) 7 years ago
tools access log service: cleanup and docs (#3494) 7 years ago
.clang-format
.gitignore
API_OVERVIEW.md
BUILD
CONTRIBUTING.md
LICENSE
README.md
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