Miek Gieben f96cf27193 mw/federation: add federation back as separate mw for k8s (#929 )

* mw/federaration

This PR add the federation back as a middleware to keep it more
contained from the main kubernetes code.

It also makes parseRequest less import and pushes this functionlity down
in the k.Entries. This minimizes (or tries to) the importance for the
qtype in the query. In the end the qtype checking should only happen
in ServeDNS - but for k8s this might proof difficult.

Numerous other cleanup in code and kubernetes tests.

* up test coverage

2017-08-18 14:45:20 +01:00

874 B

Raw Blame History

federation

The federation middleware enables federated queries to be resolved via the kubernetes middleware.

Enabling federation without also having kubernetes is a noop.

Syntax

federation [ZONES...] {
    NAME DOMAIN

Each NAME and DOMAIN defines federation membership. One entry for each. A duplicate NAME will silently overwrite any previous value.

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

Or slightly shorter:

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

874 B Raw Blame History

federation

Syntax

Examples

874 B

Raw Blame History