Kube-dns, an error due to which services between minions do not resolve, what to do?

Question

Kubernetes

According to the instructions on the Kubernetes website, when configuring kube-dns on the MASTER server, you need to take the required steps:
1. modprobe br_netfilter
2. echo '1' > /proc/sys/net/bridge/bridge-nf-call-iptables
and also on the servers (minions)
1. echo '1' > /proc/sys/net/bridge/bridge-nf-call-iptables
but not a word about "modprobe br_netfilter" , which is why we encountered an error like "kube-dns error: reply from unexpected source".
After entering the command - the problem was resolved.
The question is, is it possible to somehow check the operation of kube-dns at the time of deployment of the MASTER server and the MINION server?
P.S. all work was done on CentOS 7.6

Answer 1

Now about loading the br_netfilter module is in the kuber dock
https://kubernetes.io/docs/setup/production-enviro...
And here is a good description of how to debug kube-dns
https://kubernetes.io/docs/tasks/administer -cluste...