I am exclusively using Ubuntu 18.04 on hosts for a cluster. On occasion, I see certain hosts that have chronic DNS resolution issues. I’ve poked around quite a bit and it sounds like it may be related to the kubelet/systemd issue mentioned here.
systemd-resolvedis detected, it adds
@superseb Based on that fix, should I reasonably expect to always see
--resolv-conf=/run/systemd/resolve/resolv.conf as a kubelet arg on all my ubuntu hosts?
I’ve taken a look at kubelet args on several hosts with
docker inspect and in all cases I’m seeing:
does this mean the fix isn’t behaving as expected, or is there something else here I’m not considering?