nutritious-oxygen-89191
04/20/2023, 2:05 PM--resolv-conf
flag, how can I verify, that this configuration is actually used?rough-farmer-49135
04/20/2023, 2:12 PMkubectl exec --stdin --tty ${POD} -- /bin/bash
for a pod running on the agent that has bash and then poke around looking at /etc/resolv.conf & running nslookup, dig, ping, or whatever else was a good test for my particular concern.nutritious-oxygen-89191
04/20/2023, 2:42 PMUnable to connect to the server: dial tcp: lookup tdin on 127.0.0.53:53: server misbehaving
but kubectl exec -it <pod> -- bash
works. However, /etc/resolv.conf
does not include the nameservers
I listed in the file supplied to --resolv.conf
. Also nslookup <http://google.com|google.com>
fails with ;; connection timed out; no servers could be reached
rough-farmer-49135
04/20/2023, 2:56 PMcreamy-pencil-82913
04/20/2023, 3:36 PMdial tcp: lookup tdin on 127.0.0.53:53: server misbehavingyou did
-s tdin
didn’t you--resolv-conf
flag in the kubelet argsnutritious-oxygen-89191
04/20/2023, 4:15 PM-stdin
instead of --stdin
🤦♂️. That error is gone and I can use the command mentioned by @rough-farmer-49135. The error, however is the same nslookup <http://google.com|google.com>
fails. My flag with my modified resolv.conf
is --resolv-conf=/etc/k3s-resolv.conf
and this also comes up in the k3s logs ( the k3s-agent.service
also mentions it).creamy-pencil-82913
04/20/2023, 4:49 PMrough-farmer-49135
04/20/2023, 4:52 PMnutritious-oxygen-89191
04/20/2023, 5:31 PMcreamy-pencil-82913
04/20/2023, 5:34 PMa pod on one specific node cannot reach pods on other nodes and vice versa.That indicates a problem with your CNI traffic, not a problem with DNS
nutritious-oxygen-89191
04/21/2023, 6:24 AM