[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) e8a6b2edc5 http conn man: add tracing config for path length in tag (#8095) 5 years ago
.circleci
bazel api: organize go_proto_libraries (#8003) 5 years ago
ci
diagrams
docs api: straggler v2alpha1 -> v3alpha clone. (#8133) 5 years ago
envoy http conn man: add tracing config for path length in tag (#8095) 5 years ago
examples/service_envoy
migration api: clone v2[alpha] to v3alpha. (#8125) 5 years ago
test api: organize go_proto_libraries (#8003) 5 years ago
tools
.clang-format
.gitignore
API_OVERVIEW.md
BUILD
CONTRIBUTING.md protodoc: single source-of-truth for doc protos. (#8132) 5 years ago
LICENSE
README.md
STYLE.md
xds_protocol.rst xds: apply node identifier optimization (#7876) 6 years ago

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