Take a look 
at https://github.com/grpc/proposal/blob/master/A47-xds-federation.md which 
describes how multiple xds servers are specified in the bootstrap file and 
the federation use-case. Which gRPC language are you using?

On Monday, April 17, 2023 at 2:26:12 PM UTC+5:30 Gabriel Bordovský wrote:

> Hi,
> I work in a company that uses separate infrastructure (an internal k8s 
> cluster) for separated teams. 
> Now these teams modernize their services and often use gRPC.
> We want to employ the xDS for time-sensitive components while each team 
> providing some service is responsible for its own xDS server/control plane.
>
> We currently have an issue where one service should aggregate the results 
> of two (or possibly more) others provided by other teams.
> The idea was to create two separate gRPC clients, one for each xDS server. 
> But as for [documentation/proposal](
> https://github.com/grpc/proposal/blob/master/A27-xds-global-load-balancing.md)
>  
> the xDS client is configured using a bootstrap file specified by an 
> environmental variable `GRPC_XDS_BOOTSTRAP`. This file does not support 
> multiple servers ("xds_servers" is an array, but only the first element is 
> currently used and in the future, the others should be fallbacks).
>
> My question is if there is a recommended way to connect to multiple xDS 
> servers?
>
> The only solution I can think of now is to modify the `GRPC_XDS_BOOTSTRAP` 
> variable between the creation of the separate clients, which does not feel 
> right and I am not sure how safe it will be. It could work if the bootstrap 
> file is read when the client is initialized and is not referenced later... 
> but there could be a ton of different issues.
>
> Best regards,
> Gabriel Bordovský

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/ac921eb6-b535-442d-a7ff-a5a36729633cn%40googlegroups.com.

Reply via email to