Timo Behrendt
d360b8c970
All checks were successful
We had some inconsistencies with node configuration and dns hickups. This feature moves the coredns config into our software versioning system. Reviewed-on: #6 Co-authored-by: Timo Behrendt <t.behrendt@t00n.de> Co-committed-by: Timo Behrendt <t.behrendt@t00n.de>
48 lines
950 B
YAML
48 lines
950 B
YAML
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: coredns
|
|
namespace: kube-system
|
|
data:
|
|
Corefile: |
|
|
t00n.de:53 {
|
|
errors
|
|
forward . 192.168.0.1 192.168.0.9 192.168.0.10
|
|
cache 300
|
|
reload
|
|
}
|
|
|
|
t000-n.de:53 {
|
|
errors
|
|
forward . 192.168.0.1 192.168.0.9 192.168.0.10
|
|
cache 300
|
|
reload
|
|
}
|
|
|
|
.:53 {
|
|
errors
|
|
health
|
|
ready
|
|
kubernetes cluster.local in-addr.arpa ip6.arpa {
|
|
pods insecure
|
|
fallthrough in-addr.arpa ip6.arpa
|
|
}
|
|
hosts /etc/coredns/NodeHosts {
|
|
ttl 60
|
|
reload 15s
|
|
fallthrough
|
|
}
|
|
prometheus :9153
|
|
forward . /etc/resolv.conf
|
|
cache 30
|
|
loop
|
|
reload
|
|
loadbalance
|
|
import /etc/coredns/custom/*.override
|
|
}
|
|
import /etc/coredns/custom/*.server
|
|
NodeHosts: |
|
|
192.168.0.50 k3sh0
|
|
192.168.0.51 k3sh1
|
|
192.168.0.52 k3sh2
|