Hi all There seems to be a networking problem with k3s when using systemd. The problem manifests in that none of the kube-system management containers are able to communicate with eachother.
The root cause seems to be that systemd-networking is actively managing veth interfaces created by k3s/flannel. This happens because of '/lib/systemd/network/80-wired.network' added by the systemd recipe, which is matching on Type=ether. My fix is to modify the 80-wired.network to add 'Name=eth*'. With this in place, k3s works as expected. I am not sure what the correct upstream solution should be for Yocto? Your help would be appreciated. /Matt
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6554): https://lists.yoctoproject.org/g/meta-virtualization/message/6554 Mute This Topic: https://lists.yoctoproject.org/mt/83526656/21656 Group Owner: meta-virtualization+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
