[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) 155c38d2f3 docs: Simplify api build (#16277) 4 years ago
.circleci
bazel api: fix go importpath for OT dep (#15825) 4 years ago
ci
diagrams docs: Add sequence diagram for xDS error_detail NACK example (#15795) 4 years ago
envoy docs: Simplify api build (#16277) 4 years ago
examples/service_envoy
test
tools
versioning protos: Move simple_http_cache config proto to api (#16230) 4 years ago
.clang-format
.gitignore
API_VERSIONING.md
BUILD protos: Readd v2 legacy protos in v3 (#16338) 4 years ago
CONTRIBUTING.md docs: Improve style for inline literals and update contrib guidance (#16194) 4 years ago
LICENSE
README.md
STYLE.md protos: Update style guide to try and prevent redundant imports (#16231) 4 years ago
review_checklist.md
xds_protocol.rst docs: Remove api v2 (#16077) 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