Race condition that prevents /etc/resolve.conf to be properly updated

[kon-angelo]

How to categorize this issue?

/area control-plane
/kind bug
/platform openstack

What happened:

Provider-openstack is using a separate resolv.conf file for Kubelet as part of #375. The additional systemd unit watches for change in the run/systemd/resolve/resolv.conf and updates the kubelet-specific resolv.conf.

The race condition occurs when an update to the original resolv.conf is triggered while our unit is running causing us to miss the new event.

What you expected to happen:

For the update-resolv-conf.service to be called on every change of the original resolv.conf

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Gardener version (if relevant):
• Extension version:
• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• Others: