[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) 9a0a03eab2 docs: fix invalid transport_socket value (#9403) 5 years ago
.circleci
bazel bazel: Add load statements for proto_library (#9367) 5 years ago
ci
diagrams
docs bazel: Add load statements for proto_library (#9367) 5 years ago
envoy docs: fix invalid transport_socket value (#9403) 5 years ago
examples/service_envoy
test config: breadcrumb annotations to infer earlier API message versions. (#9166) 5 years ago
tools api/build: switch to only package level targets in API. (#8495) 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: handle field_migrate.rename (#9265) 5 years ago
BUILD
CONTRIBUTING.md api: add API_VERSIONING.md. (#8399) 5 years ago
LICENSE
README.md api: Fix link to xDS proto overview in api docs (#6966) 6 years ago
STYLE.md cleanup: remove proto comment next free annotation (#8675) 5 years ago
xds_protocol.rst docs: add explanation for ACK and NACK semantics (#9309) 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