Make -f Makefile.doc (#1487)

Add man-pages for the new plugins.

man/coredns-kubernetes.7

 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "COREDNS\-KUBERNETES" "7" "January 2018" "CoreDNS" "CoreDNS plugins"
+.TH "COREDNS\-KUBERNETES" "7" "February 2018" "CoreDNS" "CoreDNS plugins"
 .
 .SH "NAME"
 \fIkubernetes\fR \- enables the reading zone data from a Kubernetes cluster\.
@@ -32,7 +32,7 @@ With only the directive specified, the \fIkubernetes\fR plugin will default to t
 
 kubernetes [ZONES\.\.\.] {
     resyncperiod DURATION
-    endpoint URL
+    endpoint URL [URL\.\.\.]
     tls CERT KEY CACERT
     namespaces NAMESPACE\.\.\.
     labels EXPRESSION
@@ -51,7 +51,7 @@ kubernetes [ZONES\.\.\.] {
 \fBresyncperiod\fR specifies the Kubernetes data API \fBDURATION\fR period\.
 .
 .IP "\(bu" 4
-\fBendpoint\fR specifies the \fBURL\fR for a remote k8s API endpoint\. If omitted, it will connect to k8s in\-cluster using the cluster service account\. Multiple k8s API endpoints could be specified, separated by \fB,\fRs, e\.g\. \fBendpoint http://k8s\-endpoint1:8080,http://k8s\-endpoint2:8080\fR\. CoreDNS will automatically perform a healthcheck and proxy to the healthy k8s API endpoint\.
+\fBendpoint\fR specifies the \fBURL\fR for a remote k8s API endpoint\. If omitted, it will connect to k8s in\-cluster using the cluster service account\. Multiple k8s API endpoints could be specified: \fBendpoint http://k8s\-endpoint1:8080 http://k8s\-endpoint2:8080\fR\. CoreDNS will automatically perform a healthcheck and proxy to the healthy k8s API endpoint\.
 .
 .IP "\(bu" 4
 \fBtls\fR \fBCERT\fR \fBKEY\fR \fBCACERT\fR are the TLS cert, key and the CA cert file names for remote k8s connection\. This option is ignored if connecting in\-cluster (i\.e\. endpoint is not specified)\.

man/coredns-reload.7

+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "COREDNS\-RELOAD" "7" "February 2018" "CoreDNS" "CoreDNS plugins"
+.
+.SH "NAME"
+\fIreload\fR \- allows automatic reload of a changed Corefile
+.
+.SH "DESCRIPTION"
+This plugin periodically checks if the Corefile has changed by reading it and calculating its MD5 checksum\. If the file has changed, it reloads CoreDNS with the new Corefile\. This eliminates the need to send a SIGHUP or SIGUSR1 after changing the Corefile\.
+.
+.P
+The reloads are graceful \- you should not see any loss of service when the reload happens\. Even if the new Corefile has an error, CoreDNS will continue to run the old config and an error message will be printed to the log\.
+.
+.P
+In some environments (for example, Kubernetes), there may be many CoreDNS instances that started very near the same time and all share a common Corefile\. To prevent these all from reloading at the same time, some jitter is added to the reload check interval\. This is jitter from the perspective of multiple CoreDNS instances; each instance still checks on a regular interval, but all of these instances will have their reloads spread out across the jitter duration\. This isn\'t strictly necessary given that the reloads are graceful, and can be disabled by setting the jitter to \fB0s\fR\.
+.
+.P
+Jitter is re\-calculated whenever the Corefile is reloaded\.
+.
+.SH "SYNTAX"
+.
+.nf
+
+reload [INTERVAL] [JITTER]
+.
+.fi
+.
+.IP "\(bu" 4
+The plugin will check for changes every \fBINTERVAL\fR, subject to +/\- the \fBJITTER\fR duration
+.
+.IP "\(bu" 4
+\fBINTERVAL\fR and \fBJITTER\fR are Golang (durations)[https://golang\.org/pkg/time/#ParseDuration]
+.
+.IP "\(bu" 4
+Default \fBINTERVAL\fR is 30s, default \fBJITTER\fR is 15s
+.
+.IP "\(bu" 4
+Minimal value for \fBINTERVAL\fR is 2s, and for \fBJITTER\fR is 1s
+.
+.IP "\(bu" 4
+If \fBJITTER\fR is more than half of \fBINTERVAL\fR, it will be set to half of \fBINTERVAL\fR
+.
+.IP "" 0
+.
+.SH "EXAMPLES"
+Check with the default intervals:
+.
+.IP "" 4
+.
+.nf
+
+\&\. {
+    reload
+    erratic
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Check every 10 seconds (jitter is automatically set to 10 / 2 = 5 in this case):
+.
+.IP "" 4
+.
+.nf
+
+\&\. {
+    reload 10s
+    erratic
+}
+.
+.fi
+.
+.IP "" 0
+

man/coredns-route53.7

+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "COREDNS\-ROUTE53" "7" "February 2018" "CoreDNS" "CoreDNS plugins"
+.
+.SH "NAME"
+\fIroute53\fR \- enables serving zone data from AWS route53\.
+.
+.SH "DESCRIPTION"
+The route53 plugin is useful for serving zones from resource record sets in AWS route53\. This plugin only supports A and AAAA records\. The route53 plugin can be used when coredns is deployed on AWS\.
+.
+.SH "SYNTAX"
+.
+.nf
+
+route53 [ZONE:HOSTED_ZONE_ID\.\.\.] {
+    [aws_access_key AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY]
+}
+.
+.fi
+.
+.IP "\(bu" 4
+\fBZONE\fR the name of the domain to be accessed\.
+.
+.IP "\(bu" 4
+\fBHOSTED_ZONE_ID\fR the ID of the hosted zone that contains the resource record sets to be accessed\.
+.
+.IP "\(bu" 4
+\fBAWS_ACCESS_KEY_ID\fR and \fBAWS_SECRET_ACCESS_KEY\fR the AWS access key ID and secret access key to be used when query AWS (optional)\. If they are not provided, then coredns tries to access AWS credentials the same way as AWS CLI, e\.g\., environmental variables, AWS credentials file, instance profile credentials, etc\.
+.
+.IP "" 0
+.
+.SH "EXAMPLES"
+Enable route53, with implicit aws credentials:
+.
+.IP "" 4
+.
+.nf
+
+\&\. {
+    route53 example\.org\.:Z1Z2Z3Z4DZ5Z6Z7
+}
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Enable route53, with explicit aws credentials:
+.
+.IP "" 4
+.
+.nf
+
+\&\. {
+    route53 example\.org\.:Z1Z2Z3Z4DZ5Z6Z7 {
+      aws_access_key AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY
+  }
+}
+.
+.fi
+.
+.IP "" 0
+