Skip to content

Host resolution fails on pods

When deploying a pod to the beta cluster with @gandhiano, it cannot resolve DNS requests.

  • alpine: ping to 1.1.1.1 works
  • alpine: ping to 169.254.25.1 works

As dig is not available in the chosen container images, name resolution was tested from the host.

  • bm1: ping to 169.254.25.1 works
  • bm1: dig allmende.io @169.254.25.1 times out

We found these events that might be related:

root@bm1:~/alpine# kubectl get events -n kube-system
LAST SEEN   TYPE      REASON             OBJECT                   MESSAGE
<unknown>   Warning   FailedScheduling   pod/nodelocaldns-7mcwr   0/6 nodes are available: 3 Insufficient cpu, 3 node(s) didn't have free ports for the requested pod ports.
<unknown>   Warning   FailedScheduling   pod/nodelocaldns-9ln4g   0/6 nodes are available: 3 Insufficient cpu, 3 node(s) didn't have free ports for the requested pod ports.
<unknown>   Warning   FailedScheduling   pod/nodelocaldns-w5sh6   0/6 nodes are available: 3 Insufficient cpu, 3 node(s) didn't have free ports for the requested pod ports.