[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.
 
 
 
 
 
Matt Klein 3f08c922a3
access log: gRPC service config updates (#338)
7 years ago
.circleci adding check_format and fix_format (#300) 7 years ago
api access log: gRPC service config updates (#338) 7 years ago
bazel pgv: bump version to 8e6aaf5. (#319) 7 years ago
ci Adding priority to lb stats, making all priorities uint32 (#298) 7 years ago
diagrams xds: protocol writeup with sequence diagrams. (#176) 7 years ago
docs docs: document UPSTREAM_METADATA header variable (#335) 7 years ago
examples/service_envoy Add license declarations to some BUILD files. (#223) 7 years ago
test pgv: bump version to 36e0c0b, validation rules pass C++ compiler checks. (#304) 7 years ago
tools api: add some missing enum.defined_only constraints. (#330) 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 tools: automatically removing extra whitespace from rst / md (#327) 7 years ago
CONTRIBUTING.md contrib: update docs guide (#314) 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
WORKSPACE Update protobuf dependency to 3.5.0. (#244) 7 years ago
XDS_PROTOCOL.md xds_protocol: make explicit that updates only occur when resources change. (#328) 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