[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(Azure Pipelines) bdfc9f69c8 tracer: Add SkyWalking tracer (#13060) 4 years ago
.circleci
bazel tracer: Add SkyWalking tracer (#13060) 4 years ago
ci
diagrams
envoy tracer: Add SkyWalking tracer (#13060) 4 years ago
examples/service_envoy
test build: use rules_cc and use buildifier -lint to enforce it (#11399) 5 years ago
tools build: use rules_cc and use buildifier -lint to enforce it (#11399) 5 years ago
versioning Watchdog: use abort action as a default if killing is enabled. (#13523) 4 years ago
.clang-format
.gitignore
API_OVERVIEW.md
API_VERSIONING.md api: clarify that v2 is removed at EOY 2020 regardless. (#11083) 5 years ago
BUILD Watchdog: use abort action as a default if killing is enabled. (#13523) 4 years ago
CONTRIBUTING.md docs: clean up docs for azp migration (#13558) 4 years ago
LICENSE
README.md
STYLE.md
xds_protocol.rst xds: add support for TTLs (#13201) 4 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