History

Miek Gieben be1ac9fed4 plugins: remove `upstream [ADDRESS]` from docs (#2772 ) Various plugins still had this documented, the setup functions still allow it (which is fine), but update the docs that this arguments isn't there any more. Signed-off-by: Miek Gieben <miek@miek.nl>		2019-04-08 16:45:29 +01:00
..
federation.go	Remove context.Context from request.Request (#2726 )	2019-03-26 14:37:30 +00:00
federation_test.go	Stop importing testing in the main binary (#2479 )	2019-01-19 11:23:13 +00:00
kubernetes_api_test.go	Remove grpc watch functionality (#2549 )	2019-02-11 14:46:53 +00:00
log_test.go	Clean up tests logging (#1979 )	2018-07-19 16:23:06 +01:00
OWNERS	Add OWNERS file (#1486 )	2018-02-08 10:55:51 +00:00
README.md	plugins: remove `upstream [ADDRESS]` from docs (#2772 )	2019-04-08 16:45:29 +01:00
setup.go	Default to upstream to self (#2436 )	2019-01-13 16:54:49 +00:00
setup_test.go	Remove the word middleware (#1067 )	2017-09-14 09:36:06 +01:00

README.md

federation

Name

federation - enables federated queries to be resolved via the kubernetes plugin.

Description

Enabling this plugin allows Federated queries to be resolved via the kubernetes plugin.

Enabling federation without also having kubernetes is a noop.

Syntax

federation [ZONES...] {
    NAME DOMAIN
    upstream
}

Each NAME and DOMAIN defines federation membership. One entry for each. A duplicate NAME will silently overwrite any previous value.
upstream resolve the CNAME target produced by this plugin. CoreDNS will resolve External Services against itself and needs the forward plugin to be active to do so.

Examples

Here we handle all service requests in the prod and stage federations.

. {
    kubernetes cluster.local
    federation cluster.local {
        prod prod.feddomain.com
        staging staging.feddomain.com
        upstream
    }
    forward . 192.168.1.12
}