[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) a8c19f4ba2 request_id_utils: add new extension system (#10429) 5 years ago
.circleci
bazel [WiP] api: annotate files with package version status. (#10492) 5 years ago
ci
diagrams
envoy request_id_utils: add new extension system (#10429) 5 years ago
examples/service_envoy
test api/config: use resource type annotations to provide type-to-endpoint. (#9566) 5 years ago
tools api: shadowing for API protos. (#9429) 5 years ago
versioning dns_filter: Initial commit for dns_filter skeleton (#10376) 5 years ago
.clang-format
.gitignore
API_OVERVIEW.md api: Fix link to xDS proto overview in api docs (#6966) 6 years ago
API_VERSIONING.md api: document annotations and how to add an extension config. (#9672) 5 years ago
BUILD dns_filter: Initial commit for dns_filter skeleton (#10376) 5 years ago
CONTRIBUTING.md api/tools: some progress towards generalizing API version upgrade. (#10507) 5 years ago
LICENSE
README.md api: Fix link to xDS proto overview in api docs (#6966) 6 years ago
STYLE.md api/tools: some progress towards generalizing API version upgrade. (#10507) 5 years ago
xds_protocol.rst api/docs: v3 API reference documentation. (#9719) 5 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