TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 3 Projects Releases Packages Wiki Activity Actions

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
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
12 changed files with 39 additions and 60 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Makefile.release
View file

@ -26,7 +26,7 @@
# 1. Up the version in coremain/version.go # 1. Up the version in coremain/version.go
# 2. Do a make -f Makefile.doc # 2. Do a make -f Makefile.doc
# 3. go generate # 3. go generate
# 4.* Send PR to get this merged. # 4. Send PR to get this merged.
# #
# Then: # Then:
# #

2
coremain/version.go
View file

@ -2,7 +2,7 @@ package coremain
// Various CoreDNS constants. // Various CoreDNS constants.
const ( const (
CoreVersion = "1.5.1" CoreVersion = "1.5.2"
coreName = "CoreDNS" coreName = "CoreDNS"
serverType = "dns" serverType = "dns"
) )

6
man/coredns-auto.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-AUTO" 7 "June 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-AUTO" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP
@ -21,7 +21,6 @@ auto [ZONES...] {
directory DIR [REGEXP ORIGIN\_TEMPLATE] directory DIR [REGEXP ORIGIN\_TEMPLATE]
transfer to ADDRESS... transfer to ADDRESS...
reload DURATION reload DURATION
upstream
} }
.fi .fi
@ -46,9 +45,6 @@ When an address is specified a notify message will be send whenever the zone is
\fB\fCreload\fR interval to perform reloads of zones if SOA version changes and zonefiles. It specifies how often CoreDNS should scan the directory to watch for file removal and addition. Default is one minute. \fB\fCreload\fR interval to perform reloads of zones if SOA version changes and zonefiles. It specifies how often CoreDNS should scan the directory to watch for file removal and addition. Default is one minute.
Value of \fB\fC0\fR means to not scan for changes and reload. eg. \fB\fC30s\fR checks zonefile every 30 seconds Value of \fB\fC0\fR means to not scan for changes and reload. eg. \fB\fC30s\fR checks zonefile every 30 seconds
and reloads zone when serial changes. and reloads zone when serial changes.
.IP \(bu 4
\fB\fCupstream\fR defines upstream resolvers to be used resolve external names found (think CNAMEs)
pointing to external names. CoreDNS will resolve CNAMEs against itself.
.PP .PP

9
man/coredns-etcd.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-ETCD" 7 "April 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-ETCD" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP
@ -48,7 +48,6 @@ etcd [ZONES...] {
path PATH path PATH
endpoint ENDPOINT... endpoint ENDPOINT...
credentials USERNAME PASSWORD credentials USERNAME PASSWORD
upstream
tls CERT KEY CACERT tls CERT KEY CACERT
} }
@ -68,10 +67,6 @@ queries for those zones will be subject to fallthrough.
.IP \(bu 4 .IP \(bu 4
\fB\fCcredentials\fR is used to set the \fBUSERNAME\fP and \fBPASSWORD\fP for accessing the etcd cluster. \fB\fCcredentials\fR is used to set the \fBUSERNAME\fP and \fBPASSWORD\fP for accessing the etcd cluster.
.IP \(bu 4 .IP \(bu 4
\fB\fCupstream\fR upstream resolvers to be used resolve external names found in etcd (think CNAMEs)
pointing to external names. If you want CoreDNS to act as a proxy for clients, you'll need to add
the \fIforward\fP plugin.
.IP \(bu 4
\fB\fCtls\fR followed by: \fB\fCtls\fR followed by:
.RS .RS
@ -120,7 +115,6 @@ This is the default SkyDNS setup, with everything specified in full:
etcd skydns.local { etcd skydns.local {
path /skydns path /skydns
endpoint http://localhost:2379 endpoint http://localhost:2379
upstream
} }
prometheus prometheus
cache 160 skydns.local cache 160 skydns.local
@ -142,7 +136,6 @@ when resolving external pointing CNAMEs.
\&. { \&. {
etcd skydns.local { etcd skydns.local {
path /skydns path /skydns
upstream
} }
cache 160 skydns.local cache 160 skydns.local
forward . /etc/resolv.conf forward . /etc/resolv.conf

8
man/coredns-federation.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-FEDERATION" 7 "April 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-FEDERATION" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP
@ -22,7 +22,6 @@ Enabling \fIfederation\fP without also having \fIkubernetes\fP is a noop.
.nf .nf
federation [ZONES...] { federation [ZONES...] {
NAME DOMAIN NAME DOMAIN
upstream
} }
.fi .fi
@ -31,10 +30,6 @@ federation [ZONES...] {
.IP \(bu 4 .IP \(bu 4
Each \fBNAME\fP and \fBDOMAIN\fP defines federation membership. One entry for each. A duplicate Each \fBNAME\fP and \fBDOMAIN\fP defines federation membership. One entry for each. A duplicate
\fBNAME\fP will silently overwrite any previous value. \fBNAME\fP will silently overwrite any previous value.
.IP \(bu 4
\fB\fCupstream\fR resolve the \fB\fCCNAME\fR target produced by this plugin. CoreDNS
will resolve External Services against itself and needs the \fIforward\fP plugin to be active to do
so.
.SH "EXAMPLES" .SH "EXAMPLES"
@ -50,7 +45,6 @@ Here we handle all service requests in the \fB\fCprod\fR and \fB\fCstage\fR fede
federation cluster.local { federation cluster.local {
prod prod.feddomain.com prod prod.feddomain.com
staging staging.feddomain.com staging staging.feddomain.com
upstream
} }
forward . 192.168.1.12 forward . 192.168.1.12
} }

7
man/coredns-file.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-FILE" 7 "June 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-FILE" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP
@ -40,7 +40,6 @@ If you want to round-robin A and AAAA responses look at the \fIloadbalance\fP pl
file DBFILE [ZONES... ] { file DBFILE [ZONES... ] {
transfer to ADDRESS... transfer to ADDRESS...
reload DURATION reload DURATION
upstream
} }
.fi .fi
@ -55,10 +54,6 @@ When an address is specified a notify message will be sent whenever the zone is
\fB\fCreload\fR interval to perform a reload of the zone if the SOA version changes. Default is one minute. \fB\fCreload\fR interval to perform a reload of the zone if the SOA version changes. Default is one minute.
Value of \fB\fC0\fR means to not scan for changes and reload. For example, \fB\fC30s\fR checks the zonefile every 30 seconds Value of \fB\fC0\fR means to not scan for changes and reload. For example, \fB\fC30s\fR checks the zonefile every 30 seconds
and reloads the zone when serial changes. and reloads the zone when serial changes.
.IP \(bu 4
\fB\fCupstream\fR resolve external names found (think CNAMEs) pointing to external names. This is only
really useful when CoreDNS is configured as a proxy; for normal authoritative serving you don't
need \fIor\fP want to use this. CoreDNS will resolve CNAMEs against itself.
.SH "EXAMPLES" .SH "EXAMPLES"

23
man/coredns-k8s_external.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-K8S_EXTERNAL" 7 "June 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-K8S_EXTERNAL" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP
@ -97,6 +97,27 @@ Enable names under \fB\fCexample.org\fR to be resolved to in cluster DNS address
.fi .fi
.RE .RE
.PP
With the Corefile above, the following Service will get an \fB\fCA\fR record for \fB\fCtest.default.example.org\fR with IP address \fB\fC192.168.200.123\fR.
.PP
.RS
.nf
apiVersion: v1
kind: Service
metadata:
name: test
namespace: default
spec:
clusterIP: None
externalIPs:
\- 192.168.200.123
type: ClusterIP
.fi
.RE
.PP .PP
For some background see resolve external IP address For some background see resolve external IP address
\[la]https://github.com/kubernetes/dns/issues/242\[ra]. \[la]https://github.com/kubernetes/dns/issues/242\[ra].

17
man/coredns-kubernetes.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" 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" .SH "NAME"
.PP .PP
@ -21,7 +21,7 @@ to deploy CoreDNS in Kubernetes
.PP .PP
stubDomains and upstreamNameservers stubDomains and upstreamNameservers
\[la]https://kubernetes.io/blog/2017/04/configuring-private-dns-zones-upstream-nameservers-kubernetes/\[ra] \[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 .PP
This plugin can only be used once per Server Block. This plugin can only be used once per Server Block.
@ -55,7 +55,6 @@ kubernetes [ZONES...] {
labels EXPRESSION labels EXPRESSION
pods POD\-MODE pods POD\-MODE
endpoint\_pod\_names endpoint\_pod\_names
upstream
ttl TTL ttl TTL
noendpoints noendpoints
transfer to ADDRESS... 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 pod name of the pod targeted by the endpoint. If there is no pod targeted by
the endpoint, use the dashed IP address form. the endpoint, use the dashed IP address form.
.IP \(bu 4 .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 \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. 0 seconds, and the maximum is capped at 3600 seconds. Setting TTL to 0 will prevent records from being cached.
.IP \(bu 4 .IP \(bu 4
@ -163,7 +158,7 @@ Kubernetes API.
.PP .PP
Handle all queries in the \fB\fCcluster.local\fR zone. Connect to Kubernetes in-cluster. Also handle all 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 \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 .PP
.RS .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 { 10.0.0.0/17 cluster.local {
kubernetes { kubernetes {
pods verified pods verified
upstream 10.102.3.10:53
} }
} }
@ -211,7 +205,6 @@ kubernetes cluster.local {
.SH "STUBDOMAINS AND UPSTREAMNAMESERVERS" .SH "STUBDOMAINS AND UPSTREAMNAMESERVERS"
.PP .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. 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 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. or \fB\fCexample.local\fR.
@ -220,9 +213,7 @@ or \fB\fCexample.local\fR.
.nf .nf
cluster.local:53 { cluster.local:53 {
kubernetes cluster.local { kubernetes cluster.local
upstream
}
} }
example.local { example.local {
forward . 10.100.0.10:53 forward . 10.100.0.10:53

4
man/coredns-loop.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-LOOP" 7 "June 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-LOOP" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP
@ -117,7 +117,7 @@ although this can be different depending on your distribution.
Disable the local DNS cache on host nodes, and restore \fB\fC/etc/resolv.conf\fR to the original. Disable the local DNS cache on host nodes, and restore \fB\fC/etc/resolv.conf\fR to the original.
.IP \(bu 4 .IP \(bu 4
A quick and dirty fix is to edit your Corefile, replacing \fB\fCforward . /etc/resolv.conf\fR with A quick and dirty fix is to edit your Corefile, replacing \fB\fCforward . /etc/resolv.conf\fR with
the ip address of your upstream DNS, for example \fB\fCforward . 8.8.8.8\fR. But this only fixes the issue for CoreDNS, the IP address of your upstream DNS, for example \fB\fCforward . 8.8.8.8\fR. But this only fixes the issue for CoreDNS,
kubelet will continue to forward the invalid \fB\fCresolv.conf\fR to all \fB\fCdefault\fR dnsPolicy Pods, leaving them unable to resolve DNS. kubelet will continue to forward the invalid \fB\fCresolv.conf\fR to all \fB\fCdefault\fR dnsPolicy Pods, leaving them unable to resolve DNS.

2
man/coredns-reload.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-RELOAD" 7 "June 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-RELOAD" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP

12
man/coredns-route53.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-ROUTE53" 7 "April 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-ROUTE53" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP
@ -20,7 +20,6 @@ The route53 plugin can be used when coredns is deployed on AWS or elsewhere.
.nf .nf
route53 [ZONE:HOSTED\_ZONE\_ID...] { route53 [ZONE:HOSTED\_ZONE\_ID...] {
[aws\_access\_key AWS\_ACCESS\_KEY\_ID AWS\_SECRET\_ACCESS\_KEY] [aws\_access\_key AWS\_ACCESS\_KEY\_ID AWS\_SECRET\_ACCESS\_KEY]
upstream
credentials PROFILE [FILENAME] credentials PROFILE [FILENAME]
fallthrough [ZONES...] fallthrough [ZONES...]
} }
@ -41,9 +40,6 @@ to be used when query AWS (optional). If they are not provided, then coredns tri
AWS credentials the same way as AWS CLI, e.g., environmental variables, AWS credentials file, AWS credentials the same way as AWS CLI, e.g., environmental variables, AWS credentials file,
instance profile credentials, etc. instance profile credentials, etc.
.IP \(bu 4 .IP \(bu 4
\fB\fCupstream\fRis used for resolving services that point to external hosts (eg. used to resolve
CNAMEs). CoreDNS will resolve against itself.
.IP \(bu 4
\fB\fCcredentials\fR is used for reading the credential file and setting the profile name for a given \fB\fCcredentials\fR is used for reading the credential file and setting the profile name for a given
zone. zone.
.IP \(bu 4 .IP \(bu 4
@ -61,16 +57,14 @@ only queries for those zones will be subject to fallthrough.
.SH "EXAMPLES" .SH "EXAMPLES"
.PP .PP
Enable route53 with implicit AWS credentials and an upstream: Enable route53 with implicit AWS credentials and and resolve CNAMEs via 10.0.0.1:
.PP .PP
.RS .RS
.nf .nf
\&. { \&. {
route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7 { route53 example.org.:Z1Z2Z3Z4DZ5Z6Z7
upstream
}
forward . 10.0.0.1 forward . 10.0.0.1
} }

7
man/coredns-secondary.7
View file

@ -1,5 +1,5 @@
.\" Generated by Mmark Markdown Processer - mmark.nl .\" Generated by Mmark Markdown Processer - mmark.nl
.TH "COREDNS-SECONDARY" 7 "June 2019" "CoreDNS" "CoreDNS Plugins" .TH "COREDNS-SECONDARY" 7 "July 2019" "CoreDNS" "CoreDNS Plugins"
.SH "NAME" .SH "NAME"
.PP .PP
@ -35,7 +35,6 @@ A working syntax would be:
secondary [zones...] { secondary [zones...] {
transfer from ADDRESS transfer from ADDRESS
transfer to ADDRESS transfer to ADDRESS
upstream
} }
.fi .fi
@ -46,10 +45,6 @@ secondary [zones...] {
if one does not work, another will be tried. if one does not work, another will be tried.
.IP \(bu 4 .IP \(bu 4
\fB\fCtransfer to\fR can be enabled to allow this secondary zone to be transferred again. \fB\fCtransfer to\fR can be enabled to allow this secondary zone to be transferred again.
.IP \(bu 4
\fB\fCupstream\fR resolve external names found (think CNAMEs) pointing to external names. This is only
really useful when CoreDNS is configured as a proxy; for normal authoritative serving you don't
need \fIor\fP want to use this. CoreDNS will resolve CNAMEs against itself.
.PP .PP