3 ms·

I'm not familiar with w/e issue of Ubuntu caused `search domains` to end up in your resolv.conf. I'm skeptical it wasn't just a misconfiguration. At any rate, y

I'm not familiar with w/e issue of Ubuntu caused `search domains` to end up in your resolv.conf. I'm skeptical it wasn't just a misconfiguration. At any rate, you had a problem with your host configuration. The kubelet will merge the hosts resolver config with the cluster config to generate a resolv.conf file for the pods it runs, resulting in the issue you described. This can cause other annoying dns issues. It has nothing to do with CoreDNS. The only way I've found to disable this kubelet behavior is to start the kubelet with `--resolv-conf=/dev/null`

crabbone 3y ago
This is one of the series of bugs I'm referring to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103 https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981... . I'm too lazy to search for all of them. But if you pull by this thread, you should be able to find more. Don't be skeptical. It just sounds like you think you know better, when you actually have no clue.
- uberduper 3y ago
  Skeptical-o-meter just went over 9000.