xDS API Working Group (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.
 
 
 
 
 
Matthieu MOREL 555b57ec20
rules_go//proto : use go_grpc_v2 instead of go_grpc (#94)
10 months ago
bazel rules_go//proto : use go_grpc_v2 instead of go_grpc (#94) 10 months ago
ci ci: Add `go build` CI job (#78) 1 year ago
go rules_go//proto : use go_grpc_v2 instead of go_grpc (#94) 10 months ago
proposals xRFC TP2: Dynamically Generated Cacheable xDS Resources (#10) 3 years ago
test/build Duplicate all protos from udpa tree to xds tree (#17) 3 years ago
tools bazel: update configuration (#12) 3 years ago
udpa annotations: correct go_package (#80) 1 year ago
xds cel: Add canonical CEL (dev.cel.expr) fields (#89) 11 months ago
.bazelrc Fix build environment following cncf/udpa -> cncf/xds migration. (#5) 4 years ago
.bazelversion bazel: fix "missing strict dependencies" build issue (#72) 1 year ago
.gitattributes Fix build environment following cncf/udpa -> cncf/xds migration. (#5) 4 years ago
.gitignore ci: Add `go build` CI job (#78) 1 year ago
BUILD Migrate content from https://github.com/cncf/udpa. 4 years ago
DEVELOPER.md Migrate content from https://github.com/cncf/udpa. 4 years ago
LICENSE Initial commit 4 years ago
README.md Migrate content from https://github.com/cncf/udpa. 4 years ago
WORKSPACE Fix build environment following cncf/udpa -> cncf/xds migration. (#5) 4 years ago
repokitteh.star Migrate content from https://github.com/cncf/udpa. 4 years ago

README.md

xDS API Working Group (xDS-WG)

Goal

The objective of the xDS API Working Group (xDS-WG) is to bring together parties across the industry interested in a common control and configuration API for data plane proxies and load balancers, based on the xDS APIs.

Vision

The xDS vision is one of a universal data plane API, articulated at https://blog.envoyproxy.io/the-universal-data-plane-api-d15cec7a. xDS aims to provide a set of APIs that provide the de facto standard for L4/L7 data plane configuration, similar to the role played by OpenFlow at L2/L3/L4 in SDN.

The existing Envoy xDS APIs constitute the basis for this vision and will incrementally evolve towards supporting a goal of client neutrality. We will evolve the xDS APIs to support additional clients, for example data plane proxies beyond Envoy, proxyless service mesh libraries, hardware load balancers, mobile clients and beyond. We will strive to be vendor and implementation agnostic to the degree possible while not regressing on support for data plane components that have committed to xDS in production (Envoy & gRPC to date).

The xDS APIs have two delineated aspects, a transport protocol and data model, The xDS transport protocol provides a low latency versioned streaming gRPC delivery of xDS resources. The data model covers common data plane concerns such as service discovery, load balancing assignments, routing discovery, listener configuration, secret discovery, load reporting, health check delegation, etc.

Repository structure

The xDS APIs are split between this repository and https://github.com/envoyproxy/envoy/tree/main/api. Our long-term goal is to move the entire API to this repository, this will be done opportunistically over time as we generalize parts of the API to be less client-specific.

Mailing list and meetings

We have an open mailing list xds-wg@lists.cncf.io for communication and announcements. We also meet on an ad hoc basis via Zoom.

To monitor activity, you can either subscribe to a GitHub watch on this repository or join the @cncf/xds-wg team for tagging on key PRs and RFCs.