[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) 3fdb1a99c5 api: add google.protobuf.Any for opaque configs (#4739) 6 years ago
.circleci ci: remove docs/format jobs. (#619) 7 years ago
bazel Update PGV, bazel-gazelle, c-ares dependencies (#4920) 6 years ago
ci ci: remove docs/format jobs. (#619) 7 years ago
diagrams Incremental XDS proposal. (#3470) 7 years ago
docs docs: remove v1 docs (#4943) 6 years ago
envoy api: add google.protobuf.Any for opaque configs (#4739) 6 years ago
examples/service_envoy
test bootstrap: make admin field optional. (#4760) 6 years ago
tools build: update build image (#4835) 6 years ago
.clang-format adding check_format and fix_format (#300) 7 years ago
.gitignore validate: initial constraints support. (#226) 7 years ago
API_OVERVIEW.md docs: update uses of 'SDS' to 'EDS' (#4860) 6 years ago
BUILD Reconcile envoyproxy/data-plane-api and envoyproxy/envoy (#3036) 7 years ago
CONTRIBUTING.md api: trivial change to test data-plane-api mirroring. (#3086) 7 years ago
LICENSE
README.md api: some fixups post repo merge. (#3103) 7 years ago
STYLE.md api: clarify feature deprecation and replacement policy for protos. (#4747) 6 years ago
XDS_PROTOCOL.md doc: Add SDS (secret discovery service) (#4484) 6 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