[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.
 
 
 
 
 
Chris Roche 0747d643b1 admin: document /runtime endpoint (#414) 7 years ago
.circleci Create bazel rules for Go gRPC client libraries (#340) 7 years ago
api stats: support default tags with fixed value (#416) 7 years ago
bazel Refactor go BUILD targets. (#406) 7 years ago
ci Document the included check_format script (#380) 7 years ago
diagrams xds: protocol writeup with sequence diagrams. (#176) 7 years ago
docs admin: document /runtime endpoint (#414) 7 years ago
examples/service_envoy Add license declarations to some BUILD files. (#223) 7 years ago
test Refactor go BUILD targets. (#406) 7 years ago
tools Fixing fix format (#382) 7 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 api: initial STYLE.md. (#392) 7 years ago
BUILD Add license declaration in BUILD. (#412) 7 years ago
CONTRIBUTING.md api: initial STYLE.md. (#392) 7 years ago
LICENSE Add Apache 2.0 LICENSE file. (#21) 8 years ago
README.md docs: some API_OVERVIEW.md cleanup. (#264) 7 years ago
STYLE.md style clarifications (#411) 7 years ago
VERSION build: introduce VERSION file (#394) 7 years ago
WORKSPACE Create bazel rules for Go gRPC client libraries (#340) 7 years ago
XDS_PROTOCOL.md Fixing fix format (#382) 7 years ago

README.md

Data plane API

This repository 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.

Additionally, all of the documentation for the Envoy project is built directly from this repository. This allows us to keep all of our documentation next to the configuration and APIs that derive it.

Further reading