From 0d53b333dce6eb1a4895882d11c9c69f25046b5a Mon Sep 17 00:00:00 2001 From: Miek Gieben Date: Thu, 23 Jan 2020 10:58:56 +0100 Subject: [PATCH] describe locality Signed-off-by: Miek Gieben --- plugin/traffic/README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/plugin/traffic/README.md b/plugin/traffic/README.md index 9b8e3b1b3..9f0f7037f 100644 --- a/plugin/traffic/README.md +++ b/plugin/traffic/README.md @@ -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