How do I force Kubernetes CoreDNS to reload its Config Map after a change?
1
I'm running Kubernetes 1.11, and trying to configure the Kubernetes cluster to check a local name server first. I read the instructions on the Kubernetes site for customizing CoreDNS, and used the Dashboard to edit the system ConfigMap for CoreDNS. The resulting corefile value is: .:53 { errors health kubernetes cluster.local in-addr.arpa ip6.arpa { pods insecure upstream 192.168.1.3 209.18.47.61 fallthrough in-addr.arpa ip6.arpa } prometheus :9153 proxy . /etc/resolv.conf cache 30 reload } You can see the local address as the first upstream name server. My problem is that this doesn't seem to have made any impact. I have a container running with ping & nslookup, and neither will resolve names from the local name server. I'...