[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) 93e8038a99 fuzz: fixes oss-fuzz: 9621 (#3988) 7 years ago
.circleci
bazel grpc-json: handle google.api.HttpBody when building HTTP response (#3793) 7 years ago
ci
diagrams Incremental XDS proposal. (#3470) 7 years ago
docs health check: structured active healthcheck logging (#3176) 7 years ago
envoy fuzz: fixes oss-fuzz: 9621 (#3988) 7 years ago
examples/service_envoy
test Fixes #3756 by creating a new api_proto_library_internal build rule that (#3764) 7 years ago
tools access log service: cleanup and docs (#3494) 7 years ago
.clang-format
.gitignore
API_OVERVIEW.md
BUILD
CONTRIBUTING.md
LICENSE
README.md
STYLE.md thrift_proxy: move protobuf to api/config hierarchy (#3963) 7 years ago
WORKSPACE
XDS_PROTOCOL.md docs: minor typo and grammar fixups (#3984) 7 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