Known issue with systemd-resolved and latest kubeadm versions
Hi, there is a known issue [1] with operating systems using systemd-resolved (Ubuntu & Debian), and latest kubeadm versions which breaks CoreDNS in freshly initialized clusters. Until we implemented the necessary changes, the suggested workaround is to configure the following for new clusters when using one of the affected kubeadm version: ```nix yk8s.kubernetes.kubelet.defaultOptions = { resolvConf = "/run/systemd/resolve/resolv.conf"; }; ``` Please refer to the linked issue for further information. Best regards Steve [1]: https://gitlab.com/alasca.cloud/tarook/tarook/-/work_items/909 -- Steve Starke Team Lead Kubernetes Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 00 steve.starke@cloudandheat.com |www.cloudandheat.com Green, Open, Efficient. Your Cloud Service and Cloud Technology Provider from Dresden. https://www.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann
participants (1)
-
Steve Starke