New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/etc/resolv.conf #26

anton-johansson opened this Issue Jan 7, 2019 · 2 comments


None yet
2 participants
Copy link

anton-johansson commented Jan 7, 2019

The kubelet is configured with the following resolv config:
resolvConf: "/run/systemd/resolve/resolv.conf"

This implies that one is using systemd-resolvd, right? I just had systemd-resolvd disabled due to a temporary local DNS issue and manually configured my /etc/resolv.conf. This means that the directory /run/systemd/resolve/ does not exist and the kubelet is complaining about that.

It feels like it would be better to use /etc/resolv.conf directly? Not sure what implications this might cause though. If I have systemd-resolvd enabled, /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf which does not have the same contents.

We'll get back to using systemd-resolvd as soon as the issue is fixed, so it's not a superbig deal. It's just an idea/discussion.


This comment has been minimized.

Copy link

amimof commented Jan 7, 2019

I just bumbed in to this issue myself today and changing it to /etc/resolv.conf works with CoreDNS atleast.


This comment has been minimized.

Copy link

anton-johansson commented Jan 8, 2019


When digging around a bit, I found something strange though.

It looks like the KubeletConfiguration property is called resolverConfig? Maybe resolvConf is some kind of alias, but I couldn't find anything about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment