Nameserver limits were exceeded, some nameservers have been omitted.
Have you ever run into such errors on your k3s cluster?
The problem was already mentioned in a few places:
- https://vadosware.io/post/sometimes-the-problem-is-dns-on-hetzner/
- https://github.com/syself/cluster-api-provider-hetzner/issues/77
Some folks suggest modifying etc/resolved.conf, but as my node shipped with netplan (and I didn’t want to deal with that, I trust my hosting provider can handle networking), I decided to create a dedicated resolv config for kubelet needs.
It’s mentioned in the official docs
Technically, you just create a file like:
# /etc/resolv.conf.kubelet
nameserver 1.1.1.1
nameserver 2606:4700:4700::1111
And configure your pass extra kublet arg to your k3s agent:
--resolv-conf=/etc/resolv.conf.kubelet
And that should solve this quite annoying warning message as now you will have two nameservers entries with is within kubernetes limits.