I have a kubernetes cluster running on Google Container Engine (GKE) with a web server Deployment. The deployment has two replica pods, one of which is unable to make any DNS queries, regardless of whether it is querying an internal service or an external website. The container for each pod is based on Ubuntu 16.04, and I've verified that the /etc/resolv.conf is identical within the two pods. The bad pod is still able to reach external websites via ip address.

The kube-dns service seems to be running and I don't see any errors in the logs.

Is there anything else I can do to try to diagnose the problem? Unfortunately the docker image doesn't have many networking tools on it, and I can't apt-get install anything because apt can't resolve the hostnames for the package manager.

Edit: I've discovered that kube-proxy is not present on the node where the bad pod is residing. This probably explains the DNS failure, but I'm not sure why kube-proxy would be missing from the node!

  • Is kube-proxy not even in a pending state? Kubelet logs located in the node at /var/log/kubelet.log and /var/log/kube-proxy.log might reveal some additional information. You might also want to follow this document – Carlos Sep 22 '17 at 15:05
  • @Gregory Were you able to resolve this problem? If so, please post a self-answer with the resolution so to benefit the other community users encountering similar issue. – N Singh Dec 29 '17 at 15:56

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.