Add description of gRPC load-balancing and resolver options

content/docs/next-release/deployment.md

@@ -91,6 +91,12 @@ docker run \
 Or add `--reporter.type=grpc` and `--reporter.grpc.host-port=jaeger-collector.jaeger-infra.svc:14250` to use gRPC
 communication with the collector. Then the `tchannel` option can be removed.
 
+When using gRPC, you have several options for load balancing and name resolution:
+
+* Single connection and no load balancing. This is the default if you specify a single `host:port`. (example: `--reporter.grpc.host-port=jaeger-collector.jaeger-infra.svc:14250`)
+* Static list of hostnames and round-robin load balancing. This is what you get with a comma-separated list of addresses. (example: `reporter.grpc.host-port=jaeger-collector1:14250,jaeger-collector2:14250,jaeger-collector3:14250`)
+* Dynamic DNS resolution and round-robin load balancing. To get this behaviour, prefix the address with `dns:///` and gRPC will attempt to resolve the hostname using SRV records (for `grpclb` external load balancing), TXT (for `grpc_config` service configs), and A records. Refer to the [gRPC Name Resolution docs](https://github.com/grpc/grpc/blob/master/doc/naming.md) and the [dns_resolver.go implementation](https://github.com/grpc/grpc-go/blob/master/resolver/dns/dns_resolver.go) for more info. (example: `--reporter.grpc.host-port=dns:///jaeger-collector.jaeger-infra.svc:14250`)
+
 In the future we will support different service discovery systems to dynamically load balance
 across several collectors ([issue 213](https://github.com/jaegertracing/jaeger/issues/213)).
 
@@ -297,7 +303,7 @@ To view all exposed configuration options run the following command:
 ```sh
 docker run \
   -e SPAN_STORAGE_TYPE=cassandra \
-  jaegertracing/jaeger-ingester:{{< currentVersion >}} 
+  jaegertracing/jaeger-ingester:{{< currentVersion >}}
   --help \
 ```