-
Notifications
You must be signed in to change notification settings - Fork 95
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
Add XDS client #115
Add XDS client #115
Conversation
Adds a grpc client that can talk to an ADS server and forwards requests/responses from/to a cluster manager.
Just so I remember how xDS works -- the Quilkin Proxy will reach out to an xDS server through this client to get updates on the configuration state. Have I remembered that correctly? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly just me asking questions 😄
src/xds/ads_client.rs
Outdated
/// sending summarized cluster updates on the provided channel. | ||
pub async fn run( | ||
self, | ||
log: Logger, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I've been bad about enforcing this, but I like to have a source attribute for loggers, which you can see here:
quilkin/src/extensions/filters/debug.rs
Line 54 in 95cfb9d
Some(id) => base.new(o!("source" => "extensions::Debug", "id" => id)), |
So it is obvious in the logs where are coming from. Might even want to include the node_id?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added!
Adds a grpc client that can talk to an ADS server
and forwards requests/responses from/to a cluster manager.