Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Fresh deploy with CoreDNS not resolving any dns lookup #1776
kubeadm version (use
I deployed a cluster with kubeadm including calico on google cloud vm's and I cannot resolve any dns.
What you expected to happen?
That services are being resolved.
How to reproduce it (as minimally and precisely as possible)?
Trying to resolve the kubernetes svc in the default namespace:
Anything else we need to know?
Logs of coredns pods:
the same subnet for N VMs should not be an issue. it seems to me that this is GCE specific. what happens if you delete the coredns pods on the problem GCE cluster and try nslookup again?
a large chunk of the issues we get are actually caused by networking.
there are a lot of really helpful people on stack overflow, reddit and in the #kubeadm k8s slack channel that probably already run this setup!
i'm going to close this, but we can continue the discussion.
the test clusters i create, always have nodes in the same subnetwork, so not sure how subnetworks are a problem here.
removing the coredns pods doesn't solve the issue.
So I have nodes in a 10.0.0.0/8 network.
I join the 2 workers and it works all fine.
Then I create another master and workers the exact same way on 3 other nodes, but dns resolving doesn't work anymore.
So my kube-system pods have an ip in the 10 range but everything that get deployed after cluster creation gets the calico pod range.
a CIDR conflict?
you could try the weave-net or Cilium pod network plugins instead of Calico: