Gogs
bef6e57d0d
first commit
|
hai 1 mes | |
|---|---|---|
| .. | ||
| .circleci | hai 1 mes | |
| bazel | hai 1 mes | |
| ci | hai 1 mes | |
| contrib | hai 1 mes | |
| envoy | hai 1 mes | |
| examples | hai 1 mes | |
| test | hai 1 mes | |
| tools | hai 1 mes | |
| versioning | hai 1 mes | |
| .clang-format | hai 1 mes | |
| .gitignore | hai 1 mes | |
| API_VERSIONING.md | hai 1 mes | |
| BUILD | hai 1 mes | |
| CONTRIBUTING.md | hai 1 mes | |
| LICENSE | hai 1 mes | |
| README.md | hai 1 mes | |
| STYLE.md | hai 1 mes | |
| buf.lock | hai 1 mes | |
| buf.yaml | hai 1 mes | |
| review_checklist.md | hai 1 mes | |
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:
- https://github.com/envoyproxy/envoy/tree/main/api - canonical read/write home for the APIs.
- https://github.com/envoyproxy/data-plane-api - read-only mirror of https://github.com/envoyproxy/envoy/tree/main/api, providing the ability to consume the data plane APIs without the Envoy implementation.