kubelet.service not waiting for network-online.target

[rosti]

Whenever kubeadm detects a system that has systemd-resolved running, it would provision the kubelet on the local node with a resolv.conf overwrite - /run/systemd/resolve/resolv.conf.

However, some kubeadm users have discovered an issue during system boot. The kubelet can end up in a race with the systemd-resolved service and actually startup loads with empty or incorrect resolve.conf files.

The race is caused by the fact that the kubelet.service file does not indicate dependence on the network-online.target.

xref kubernetes/kubeadm#2111

/kind bug
/assign

[neolit123]

/priority important-longterm
cc @BenTheElder @aojea

[BenTheElder]

Thanks for the heads up, the resolv.conf in kind isn't systemd managed though.

I could definitely see this being an issue in prod systems 😬

[justaugustus]

Closed via #1250.
/close

[k8s-ci-robot]

@justaugustus: Closing this issue.

In response to this:

Closed via #1250.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.