Which approach preserves cloud-init DNS settings across reboots in k3os?
The goal is to keep custom DNS servers supplied via cloud-init after a k3os node reboots. During early boot, cloud-init writes the nameservers to /etc/resolv.conf, but k3os later runs a DNS reconciliation loop that regenerates /etc/resolv.conf from static files in /etc/rancher/k3os/dns, overwriting the cloud-init values unless those files are also updated. I