Skip to content

C
Coredns
Commit 39f6ca5d authored by Miek Gieben's avatar Miek Gieben
Browse files
Options

more words 

Signed-off-by: default avatarMiek Gieben <miek@miek.nl>
parent 0d53b333
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 1 deletion
plugin/traffic/README.md
View file @ 39f6ca5d
...@@ -72,7 +72,8 @@ traffic TO... { ...@@ -72,7 +72,8 @@ traffic TO... {
considered local traffic. Each **REGION,ZONE,SUBZONE** will be used to match clusters again while generating 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 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: there are 3 regions, US, EU, ASIA, and this CoreDNS is running in EU, you can use:
`locality EU,*,* US,*,*, ASIA,*,*`. `locality EU,*,* US,*,*, ASIA,*,*`. Only when the cluster's locality isn't UNKNOWN will this
matching happen.
* `tls` **CERT** **KEY** **CA** define the TLS properties for gRPC connection. If this is omitted an * `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 insecure connection is attempted. From 0 to 3 arguments can be provided with the meaning as described below
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment