-
Notifications
You must be signed in to change notification settings - Fork 689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace GRPC server with envoy's go-control-plane #2134
Comments
Note that this doesn't solve configuration snapshot consistency issues (see various issues in the go-control-plane repo). |
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by replacing the current XDS server implementation with the envoyproxy/go-control-plane impl. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by implementing the Envoy go-control-plane to replace Contour's current custom xDS gRPC server. The change utilizes snapshots as a way to represent a versioned point in time representation of the xDS resources (RDS, CDS, EDS, LDS, SDS). When the dag is rebuilt or an endpoint changes, a new snapshot is created with the updated caches for each xDS resource type. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by implementing the Envoy go-control-plane to replace Contour's current custom xDS gRPC server. The change utilizes snapshots as a way to represent a versioned point in time representation of the xDS resources (RDS, CDS, EDS, LDS, SDS). When the dag is rebuilt or an endpoint changes, a new snapshot is created with the updated caches for each xDS resource type. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by implementing the Envoy go-control-plane to replace Contour's current custom xDS gRPC server. The change utilizes snapshots as a way to represent a versioned point in time representation of the xDS resources (RDS, CDS, EDS, LDS, SDS). When the dag is rebuilt or an endpoint changes, a new snapshot is created with the updated caches for each xDS resource type. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by implementing the Envoy go-control-plane to replace Contour's current custom xDS gRPC server. The change utilizes snapshots as a way to represent a versioned point in time representation of the xDS resources (RDS, CDS, EDS, LDS, SDS). When the dag is rebuilt or an endpoint changes, a new snapshot is created with the updated caches for each xDS resource type. Signed-off-by: Steve Sloka <[email protected]>
Fixes projectcontour#2134 by implementing the Envoy go-control-plane to replace Contour's current custom xDS gRPC server. The change utilizes snapshots as a way to represent a versioned point in time representation of the xDS resources (RDS, CDS, EDS, LDS, SDS). When the dag is rebuilt or an endpoint changes, a new snapshot is created with the updated caches for each xDS resource type. Signed-off-by: Steve Sloka <[email protected]>
@davinci26 @clayton-gonsalves @izturn do any of you have non-production environments where you could try switching to using the go-control-plane xDS server instead of the legacy Contour impl and see if you encounter any problems? We've been running E2E's daily with it enabled with success but some more real-world testing (ideally looking at performance/scale in addition to correctness) would be great too before we consider flipping the default in Contour. Specifically, this involves setting the following in the Contour config file: server:
xds-server-type: envoy For reference here is a PR that changes the default to be |
@davinci26 @clayton-gonsalves @izturn (or anyone else) just a gentle nudge here, is this change something you could test in a non-prod environment? |
@skriss sorry had this message on draft. We are working on a bunch of items to improve the operational stability of Contour so we are not taking many upstream changes but I think we should be able to take it and test it out in a couple of weeks from now. Does this work? |
That'd be great, thanks! We may make the change upstream soon-ish anyway to let CI start running regularly on it. It has already been running in our nightly tests and seems pretty stable. |
selfnote: consider effects of Endpoint updates |
@skriss, we have some non-prod environments, but we don't put a lot of payloads on them, we will try it later |
@skriss Based on our limited testing, everything is fine |
The default xDS server implementation is now `envoy`, i.e. the go-control-plane implementation. Updates projectcontour#2134. Signed-off-by: Steve Kriss <[email protected]>
- Triggers only EDS updates when endpoints change - Does not trigger EDS updates when only non-endpoints change Updates #2134. Signed-off-by: Steve Kriss <[email protected]>
The default xDS server implementation is now `envoy`, i.e. the go-control-plane implementation. Updates projectcontour#2134. Signed-off-by: Steve Kriss <[email protected]>
Updates #2134. Signed-off-by: Steve Kriss <[email protected]>
The default xDS server implementation is now `envoy`, i.e. the go-control-plane implementation. Updates #2134. Signed-off-by: Steve Kriss <[email protected]>
- Triggers only EDS updates when endpoints change - Does not trigger EDS updates when only non-endpoints change Updates projectcontour#2134. Signed-off-by: Steve Kriss <[email protected]>
Updates projectcontour#2134. Signed-off-by: Steve Kriss <[email protected]>
The default xDS server implementation is now `envoy`, i.e. the go-control-plane implementation. Updates projectcontour#2134. Signed-off-by: Steve Kriss <[email protected]>
Remaining work here is to fully remove the Contour xDS server option and implementation, can plan to do this for the 1.31 release assuming no major issues post-1.29. release. |
Fields are planned to be removed in the 1.31 release. Updates projectcontour#2134. Signed-off-by: Steve Kriss <[email protected]>
Fields are planned to be removed in the 1.31 release. Updates #2134. Signed-off-by: Steve Kriss <[email protected]>
Fields are planned to be removed in the 1.31 release. Updates projectcontour#2134. Signed-off-by: Steve Kriss <[email protected]> Signed-off-by: Geoff Macartney <[email protected]>
Fields are planned to be removed in the 1.31 release. Updates projectcontour#2134. Signed-off-by: Steve Kriss <[email protected]> Signed-off-by: Saman Mahdanian <[email protected]>
I looked ad go-control-plane a bit and we ought to be able to use it to replace our custom xDS code. The interfaces are a bit different, but we should be able to bind the DAG in without a lot of trouble. This likely gives us ADS support for free.
Related #1286
The text was updated successfully, but these errors were encountered: