Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-27 08:14:18 -04:00
Code Issues Packages Projects Releases Wiki Activity

Bump version to 1.5.2 (#2969)

Browse Source 
Run through the motions; create manual pages. Run go generate for good
measure. Fix typo in Makefile.release while at it.

Signed-off-by: Miek Gieben <miek@miek.nl>
This commit is contained in:
Miek Gieben
2019-07-03 19:47:38 +01:00
committed by GitHub
parent bb9df3122d
commit d933f635af
12 changed files with 39 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
man/coredns-kubernetes.7
View File

@@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-KUBERNETES" 7 "June 2019" "CoreDNS" "CoreDNS Plugins"
.TH "COREDNS-KUBERNETES" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME"
.PP
@@ -21,7 +21,7 @@ to deploy CoreDNS in Kubernetes
.PP
stubDomains and upstreamNameservers
\[la]https://kubernetes.io/blog/2017/04/configuring-private-dns-zones-upstream-nameservers-kubernetes/\[ra]
are implemented via the \fIforward\fP plugin and kubernetes \fIupstream\fP. See the examples below.
are implemented via the \fIforward\fP plugin. See the examples below.
.PP
This plugin can only be used once per Server Block.
@@ -55,7 +55,6 @@ kubernetes [ZONES...] {
labels EXPRESSION
pods POD\-MODE
endpoint\_pod\_names
upstream
ttl TTL
noendpoints
transfer to ADDRESS...
@@ -125,10 +124,6 @@ follows: Use the hostname of the endpoint, or if hostname is not set, use the
pod name of the pod targeted by the endpoint. If there is no pod targeted by
the endpoint, use the dashed IP address form.
.IP \(bu 4
\fB\fCupstream\fR defines the upstream resolvers used for resolving services
that point to external hosts (aka External Services, aka CNAMEs). CoreDNS
will resolve External Services against itself.
.IP \(bu 4
\fB\fCttl\fR allows you to set a custom TTL for responses. The default is 5 seconds. The minimum TTL allowed is
0 seconds, and the maximum is capped at 3600 seconds. Setting TTL to 0 will prevent records from being cached.
.IP \(bu 4
@@ -163,7 +158,7 @@ Kubernetes API.
.PP
Handle all queries in the \fB\fCcluster.local\fR zone. Connect to Kubernetes in-cluster. Also handle all
\fB\fCin-addr.arpa\fR \fB\fCPTR\fR requests for \fB\fC10.0.0.0/17\fR . Verify the existence of pods when answering pod
requests. Resolve upstream records against \fB\fC10.102.3.10\fR. Note we show the entire server block here:
requests.
.PP
.RS
@@ -172,7 +167,6 @@ requests. Resolve upstream records against \fB\fC10.102.3.10\fR. Note we show th
10.0.0.0/17 cluster.local {
kubernetes {
pods verified
upstream 10.102.3.10:53
}
}
@@ -211,7 +205,6 @@ kubernetes cluster.local {
.SH "STUBDOMAINS AND UPSTREAMNAMESERVERS"
.PP
Here we use the \fIforward\fP plugin to implement a stubDomain that forwards \fB\fCexample.local\fR to the nameserver \fB\fC10.100.0.10:53\fR.
The \fIupstream\fP option in the \fIkubernetes\fP plugin means that ExternalName services (CNAMEs) will be resolved using the respective proxy.
Also configured is an upstreamNameserver \fB\fC8.8.8.8:53\fR that will be used for resolving names that do not fall in \fB\fCcluster.local\fR
or \fB\fCexample.local\fR.
@@ -220,9 +213,7 @@ or \fB\fCexample.local\fR.
.nf
cluster.local:53 {
kubernetes cluster.local {
upstream
}
kubernetes cluster.local
}
example.local {
forward . 10.100.0.10:53