[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) 46bf7af76c ext_authz: Add dynamic metadata field to CheckResponse (#12677) 4 years ago
.circleci
bazel Revert "pgv: update (#12025)" (#12100) 5 years ago
ci
diagrams
envoy ext_authz: Add dynamic metadata field to CheckResponse (#12677) 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 tap: factor out the TAP filter matcher for later reuse in other filters (#12429) 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 Fix proto_sync.py (#12434) 4 years ago
CONTRIBUTING.md Validating config in docs (#11394) 5 years ago
LICENSE
README.md
STYLE.md api: tools/docs to support v2 freeze, v4alpha cut. (#10636) 5 years ago
xds_protocol.rst docs: clarify xDS resource instance version semantics (#12580) 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