[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) 3ce6441c05 listener: undeprecate bind_to_port (#14480) 4 years ago
.circleci
bazel deps: update PGV (#14571) 4 years ago
ci
diagrams
envoy listener: undeprecate bind_to_port (#14480) 4 years ago
examples/service_envoy
test deps: update protobuf to 3.14 (#14253) 4 years ago
tools
versioning http: add support for skip filter match action (#14275) 4 years ago
.clang-format
.gitignore
API_VERSIONING.md api: define an API breaking change grace period. (#14390) 4 years ago
BUILD http: add support for skip filter match action (#14275) 4 years ago
CONTRIBUTING.md
LICENSE
README.md xds: refactor and update API principles. (#14243) 4 years ago
STYLE.md xds: refactor and update API principles. (#14243) 4 years ago
xds_protocol.rst docs: fix typo in xDS docs (#14541) 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