dualstack user guide #1357
dualstack user guide #1357
Conversation
| and that information is communicated to the Load Balancing Policy. | ||
|
|
||
| Note that the only name resolver implementation that gRPC provides is a | ||
| DNS resolver, which does not support dualstack backends. This is |
There was a problem hiding this comment.
It won't be clear to users what "does not support" means here. You can use dualstack backends with pick_first. Maybe the earlier paragraph about load balancing policies needs to call out that nothing special needs to happen for the default policy, pick_first. But if using a different policy it probably needs NR support? And then you can use round_robin as an example when explaining the twice-the-load problem.
| one of the two protocols may actually be routable between a given | ||
| client and endpoint, clients need to try both addresses to see which | ||
| one will work. To minimize connection attempt latency, it is also | ||
| desirable for clients to attempt to connect to multiple addresses in |
There was a problem hiding this comment.
"it is also desirable" doesn't say what is actually done or who is responsible for it. "To minimize connection attempt latency, gRPC clients will attempt..."?
| 2. Use an xDS control plane that can communicate multiple addresses | ||
| per endpoint to the client. For more information, consult the | ||
| documentation for your xDS control plane. |
There was a problem hiding this comment.
I was going to say this should link to some grpc xds documentation for how to set up your client to talk to your control plane, but...I can't find anything appropriately user-facing. Should we link to https://github.com/grpc/proposal/blob/master/A27-xds-global-load-balancing.md for now?
Should we create another guide that covers how to set up a bootstrap file and create an xds-enabled grpc client (and server, possibly separately)?
| |----------|------------------|----------------------------------------| | ||
| | C++ | | C++ resolver API not yet public. | | ||
| | Go | | Go dualstack support not yet complete. | | ||
| | Java | [Java example] | | |
There was a problem hiding this comment.
Maybe indicate that both Java and Go have only experimental support for custom LB policies?
@temawi