Chris O'Haver 6beeabc47c 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

2018-10-15 12:43:03 -04:00

1.3 KiB

Raw Blame History

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 [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

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
    }
}

Or slightly shorter:

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

1.3 KiB Raw Blame History