Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-28 08:44:17 -04:00
Code Issues Packages Projects Releases Wiki Activity

Add words on grpc service config

Browse Source 
Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2020-03-03 12:32:46 +01:00
parent 885514b670
commit 5cce32db15
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
plugin/traffic/README.md
View File

@@ -35,6 +35,10 @@ enough to select the best one. When SRV records are returned, the endpoint DNS n
`endpoint-<N>.<cluster>.<zone>` that carries the IP address. Querying for these synthesized names `endpoint-<N>.<cluster>.<zone>` that carries the IP address. Querying for these synthesized names
works as well. works as well.
[gRPC Service Config](https://github.com/grpc/proposal/blob/master/A2-service-configs-in-dns.md),
when queried for `_grpc_config.<cluster> TXT` such config will be returned. Currently the config
itself is staticly defined from the properties given in the *traffic* plugin itself.
Load reporting is not supported for the following reason: A DNS query is done by a resolver. Load reporting is not supported for the following reason: A DNS query is done by a resolver.
Behind this resolver (which can also cache) there may be many clients that will use this reply. The Behind this resolver (which can also cache) there may be many clients that will use this reply. The
responding server (CoreDNS) has no idea how many clients use this resolver. So reporting a load of responding server (CoreDNS) has no idea how many clients use this resolver. So reporting a load of