Nameserver limit exceeded about hcloud-cloud-controller-manager HOT 3 CLOSED

Hey @MichaelVoelkel,

are you talking about this warning message?

Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 2a01:4ff:ff00::add:2 2a01:4ff:ff00::add:1 185.12.64.2

This warning is actually benign and more about a bug in libc than anything else. Kubernetes still works as expected, but only passes 3 out of the 4 defined Nameserver IPs to Pods.

This seems to block cloud-controller-manager as it needs fewer entries.

What issues do you see with HCCM? The warning message should show up for every single Pod, not only HCCM.

from hcloud-cloud-controller-manager.

Having looked deeper (that is, into the actual logs of the container), there was actually a very different problem.

Still, is it not a problem if only 3/4 nameservers are transmitted?

Another problem was that not all env vars from some tutorial were really moved to kubelet, in particular the right resolv.conf. The right resolv.conf also has four namesevers but for some reason this does not lead to errors.

So, not sure, but yeah, latest info seems to indicate it's not on this CCM...

from hcloud-cloud-controller-manager.

Still, is it not a problem if only 3/4 nameservers are transmitted?

Multiple nameservers are provided for redundancy reasons. Removing one IP from the list might reduce the total availability, but as long as there is still one server available this should not be a problem.

Closing as there is no evident issue with HCCM

from hcloud-cloud-controller-manager.