plugin/federation: Add upstream option to federation (#2177)

* add upstream

* add upstream

* debug ci

* debug ci

* set context

* update readme

* update readme

* remove empty if
This commit is contained in:
Chris O'Haver
2018-10-15 12:43:03 -04:00
committed by Francois Tur
parent 1847ef6bd3
commit 6beeabc47c
3 changed files with 28 additions and 3 deletions

View File

@@ -17,11 +17,16 @@ Enabling *federation* without also having *kubernetes* is a noop.
~~~
federation [ZONES...] {
NAME DOMAIN
upstream [ADDRESS...]
}
~~~
* Each **NAME** and **DOMAIN** defines federation membership. One entry for each. A duplicate
**NAME** will silently overwrite any previous value.
* `upstream` [**ADDRESS**...] defines the upstream resolvers used for resolving the `CNAME` target
produced by this plugin. If no **ADDRESS** is given, CoreDNS
will resolve External Services against itself. **ADDRESS** can be an IP, an IP:port, or a path
to a file structured like resolv.conf.
## Examples
@@ -33,6 +38,7 @@ Here we handle all service requests in the `prod` and `stage` federations.
federation cluster.local {
prod prod.feddomain.com
staging staging.feddomain.com
upstream
}
}
~~~
@@ -45,6 +51,7 @@ cluster.local {
federation {
prod prod.feddomain.com
staging staging.feddomain.com
upstream
}
}
~~~