[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) ff1d59c377 mongo_proxy: support configurable command list for metrics (#13494) 4 years ago
.circleci
bazel Dependencies: refactor API dependencies, fix proto JSON block, finish pip install hashes (#13343) 4 years ago
ci
diagrams
envoy mongo_proxy: support configurable command list for metrics (#13494) 4 years ago
examples/service_envoy
test build: use rules_cc and use buildifier -lint to enforce it (#11399) 5 years ago
tools build: use rules_cc and use buildifier -lint to enforce it (#11399) 5 years ago
versioning Upstream envoyproxy/envoy-wasm. (#12546) 4 years ago
.clang-format
.gitignore
API_OVERVIEW.md
API_VERSIONING.md
BUILD Upstream envoyproxy/envoy-wasm. (#12546) 4 years ago
CONTRIBUTING.md Validating config in docs (#11394) 4 years ago
LICENSE
README.md
STYLE.md
xds_protocol.rst http2: add optional connection ping/keepalive (#13152) 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