mirror of
https://github.com/coredns/coredns.git
synced 2025-10-27 08:14:18 -04:00
generate doc for 1.1.3 (#1832)
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
.\" generated with Ronn/v0.7.3
|
||||
.\" http://github.com/rtomayko/ronn/tree/0.7.3
|
||||
.
|
||||
.TH "COREDNS\-KUBERNETES" "7" "April 2018" "CoreDNS" "CoreDNS plugins"
|
||||
.TH "COREDNS\-KUBERNETES" "7" "May 2018" "CoreDNS" "CoreDNS plugins"
|
||||
.
|
||||
.SH "NAME"
|
||||
\fIkubernetes\fR \- enables the reading zone data from a Kubernetes cluster\.
|
||||
@@ -43,6 +43,7 @@ kubernetes [ZONES\.\.\.] {
|
||||
endpoint_pod_names
|
||||
upstream [ADDRESS\.\.\.]
|
||||
ttl TTL
|
||||
transfer to ADDRESS\.\.\.
|
||||
fallthrough [ZONES\.\.\.]
|
||||
}
|
||||
.
|
||||
@@ -93,8 +94,14 @@ kubernetes [ZONES\.\.\.] {
|
||||
\fBnoendpoints\fR will turn off the serving of endpoint records by disabling the watch on endpoints\. All endpoint queries and headless service queries will result in an NXDOMAIN\.
|
||||
.
|
||||
.IP "\(bu" 4
|
||||
\fBtransfer\fR enables zone transfers\. It may be specified multiples times\. \fBTo\fR signals the direction (only \fBto\fR is alllow)\. \fBADDRESS\fR must be denoted in CIDR notation (127\.0\.0\.1/32 etc\.) or just as plain addresses\. The special wildcard \fB*\fR means: the entire internet\. Sending DNS notifies is not supported\.
|
||||
.
|
||||
.IP "\(bu" 4
|
||||
\fBfallthrough\fR \fB[ZONES\.\.\.]\fR If a query for a record in the zones for which the plugin is authoritative results in NXDOMAIN, normally that is what the response will be\. However, if you specify this option, the query will instead be passed on down the plugin chain, which can include another plugin to handle the query\. If \fB[ZONES\.\.\.]\fR is omitted, then fallthrough happens for all zones for which the plugin is authoritative\. If specific zones are listed (for example \fBin\-addr\.arpa\fR and \fBip6\.arpa\fR), then only queries for those zones will be subject to fallthrough\.
|
||||
.
|
||||
.IP "\(bu" 4
|
||||
\fBignore empty_service\fR return NXDOMAIN for services without any ready endpoint addresses (e\.g\. ready pods)\. This allows the querying pod to continue searching for the service in the search path\. The search path could, for example, include another kubernetes cluster\.
|
||||
.
|
||||
.IP "" 0
|
||||
.
|
||||
.SH "HEALTH"
|
||||
|
||||
Reference in New Issue
Block a user