https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
that…. is not a resolv.conf
a
in ubuntu it is handled by systemd, anyway # resolvectl status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Current DNS Server: 100.64.43.100 DNS Servers: 100.64.43.100 10.114.81.10
s
Had similar situation and created a specific resolv.conf for k3s and added this to k3s startup arguments:
Copy code
--resolv-conf=/data/kubernetes/resolv.conf
AFAIK Kubernetes and systemd-resolved are not on friendly terms
✅ 1
a
all right than, tnx both of you guys!
c
you still have a resolv.conf on the host, which is what the kubelet reads. it does not read systemd-resolved config files.
s
It might be using /run/systemd/resolve/resolv.conf unless --resolv-conf is specified since it does not understand/cannot use resolv-stub.conf since it tries to reach nameserver on localhost
I think the problem is that the auto-generated resolv.conf by systemd includes both the manually entered entries in resolved.conf (from systemd) and entries received by the DHCP server (if one exists). That's why there are more than three entries.
a
ja, you both right. it turned out there were 4 dns in resolv.conf. 2 coming from the resolved.conf (in systemd) and 2 coming from netplan thanks again for the help!
5 Views
Open in Slack
PreviousNext
Powered by