Fix warning when using 3 upstream DNS servers

Warning: Nameserver limits were exceeded, some nameservers have been omitted,
the applied nameserver line is: 10.96.0.10 8.8.8.8 8.8.4.4

Removing 3rd DNS server entry fixes the issue.

Change-Id: I14fae0d884223050eb3106b4a9cf1adde01def8f
This commit is contained in:
Kaspars Skels 2019-07-17 15:18:46 -05:00
parent b15899667f
commit a9219125fc
5 changed files with 5 additions and 18 deletions

View File

@ -71,14 +71,6 @@ metadata:
dest: dest:
path: .values.conf.coredns.corefile path: .values.conf.coredns.corefile
pattern: '(UPSTREAM2)' pattern: '(UPSTREAM2)'
- src:
schema: pegleg/CommonAddresses/v1
name: common-addresses
path: .dns.upstream_servers[2]
dest:
path: .values.conf.coredns.corefile
pattern: '(UPSTREAM3)'
data: data:
chart_name: coredns chart_name: coredns
release: coredns release: coredns
@ -107,10 +99,9 @@ data:
fallthrough in-addr.arpa ip6.arpa fallthrough in-addr.arpa ip6.arpa
upstream UPSTREAM1 upstream UPSTREAM1
upstream UPSTREAM2 upstream UPSTREAM2
upstream UPSTREAM3
} }
prometheus :9153 prometheus :9153
forward . UPSTREAM1 UPSTREAM2 UPSTREAM3 forward . UPSTREAM1 UPSTREAM2
cache 30 cache 30
} }

View File

@ -60,8 +60,7 @@ data:
upstream_servers: upstream_servers:
- 8.8.8.8 - 8.8.8.8
- 8.8.4.4 - 8.8.4.4
- 208.67.222.222 upstream_servers_joined: 8.8.8.8,8.8.4.4
upstream_servers_joined: 8.8.8.8,8.8.4.4,208.67.222.222
genesis: genesis:
hostname: REPLACEME hostname: REPLACEME

View File

@ -32,10 +32,9 @@ data:
upstream_servers: upstream_servers:
- 8.8.8.8 - 8.8.8.8
- 8.8.4.4 - 8.8.4.4
- 208.67.222.222
# Repeat the same values as above, but formatted as a common separated # Repeat the same values as above, but formatted as a common separated
# string # string
upstream_servers_joined: 8.8.8.8,8.8.4.4,208.67.222.222 upstream_servers_joined: 8.8.8.8,8.8.4.4
# NEWSITE-CHANGEME: FQDN for ingress (i.e. "publicly facing" access point) # NEWSITE-CHANGEME: FQDN for ingress (i.e. "publicly facing" access point)
# Choose FQDN according to the ingress/public FQDN naming conventions at # Choose FQDN according to the ingress/public FQDN naming conventions at
# the top of this document. # the top of this document.

View File

@ -36,10 +36,9 @@ data:
upstream_servers: upstream_servers:
- 8.8.8.8 - 8.8.8.8
- 8.8.4.4 - 8.8.4.4
- 208.67.222.222
# Repeat the same values as above, but formatted as a common separated # Repeat the same values as above, but formatted as a common separated
# string # string
upstream_servers_joined: 8.8.8.8,8.8.4.4,208.67.222.222 upstream_servers_joined: 8.8.8.8,8.8.4.4
# NEWSITE-CHANGEME: FQDN for ingress (i.e. "publicly facing" access point) # NEWSITE-CHANGEME: FQDN for ingress (i.e. "publicly facing" access point)
# Choose FQDN according to the ingress/public FQDN naming conventions at # Choose FQDN according to the ingress/public FQDN naming conventions at
# the top of this document. # the top of this document.

View File

@ -40,10 +40,9 @@ data:
upstream_servers: upstream_servers:
- 8.8.8.8 - 8.8.8.8
- 8.8.4.4 - 8.8.4.4
- 208.67.222.222
# Repeat the same values as above, but formatted as a common separated # Repeat the same values as above, but formatted as a common separated
# string # string
upstream_servers_joined: 8.8.8.8,8.8.4.4,208.67.222.222 upstream_servers_joined: 8.8.8.8,8.8.4.4
# NEWSITE-CHANGEME: FQDN for ingress (i.e. "publicly facing" access point) # NEWSITE-CHANGEME: FQDN for ingress (i.e. "publicly facing" access point)
# Choose FQDN according to the ingress/public FQDN naming conventions at # Choose FQDN according to the ingress/public FQDN naming conventions at
# the top of this document. # the top of this document.