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

describe locality

Browse Source 
Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2020-01-23 10:58:56 +01:00
parent 246b8ac89c
commit 0d53b333dc
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
plugin/traffic/README.md
View File

@@ -60,13 +60,19 @@ The extended syntax is available if you want more control.
~~~
traffic TO... {
node ID
locality REGION,ZONE,SUBZONE [REGION,ZONE,SUBZONE]...
tls CERT KEY CA
tls_servername NAME
ignore_health
}
~~~
* node **ID** is how *traffic* identifies itself to the control plane. This defaults to `coredns`.
* `node` **ID** is how *traffic* identifies itself to the control plane. This defaults to `coredns`.
* `locality` has a list of **REGION,ZONE,SUBZONE**s. These tell *traffic* where its running and what should be
considered local traffic. Each **REGION,ZONE,SUBZONE** will be used to match clusters again while generating
responses. The list should descend in proximity. A `*` describes a wildcard match. I.e. when
there are 3 regions, US, EU, ASIA, and this CoreDNS is running in EU, you can use:
`locality EU,*,* US,*,*, ASIA,*,*`.
* `tls` **CERT** **KEY** **CA** define the TLS properties for gRPC connection. If this is omitted an
insecure connection is attempted. From 0 to 3 arguments can be provided with the meaning as described below