[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) 2b941bd6c8 upstream: respect overprovisioning factor for static/strict dns (#5091) 6 years ago
.circleci
bazel deps: bump pgv to fix static initialization fiasco (#5044) 6 years ago
ci
diagrams Incremental XDS proposal. (#3470) 7 years ago
docs rate-limit: remove legacy service support (#4881) 6 years ago
envoy upstream: respect overprovisioning factor for static/strict dns (#5091) 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
.gitignore
API_OVERVIEW.md docs: update uses of 'SDS' to 'EDS' (#4860) 6 years ago
BUILD
CONTRIBUTING.md
LICENSE
README.md
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