On Mon, Jun 14, 2021 at 6:27 AM Matt Spencer <[email protected]> wrote: > > 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. >
This particular issue is known, in the sense that we have run into it before. At a minimum, I need to warn about it in the k3s README files. I created the cni bbclass to manage potentially conflicting networking configs on that front, but systemd-networking is yet another variable. We don't want to globally make it conflict, since someone might have a working networkd config that they want to use, and exactly how networking is set up, tends to be more of a distro feature. So the recipes need to tread carefully. Which takes me back to the README, and an enhancement to the cni-networking bbclass to be more generic and pick up / warn on configuration issues like this. bruce > /Matt > > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6555): https://lists.yoctoproject.org/g/meta-virtualization/message/6555 Mute This Topic: https://lists.yoctoproject.org/mt/83526656/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
