networkd: prevent networkd interference with cilium_vxlan interface #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cilium's cilium_vxlan interface was getting the default networkd setup
applied which tries to attach an IP address through DHCP. This meant
that the interface was stuck in this "configuring" state by networkd
and now since somewhere between systemd 247.3 and 247.6 this also
causes a disruption, reported in
flatcar/Flatcar#455
Set the cilium_vxlan interface to be not managed by networkd's default
setup with DHCP as it's managed by Cilium.
How to use
To verify, check
networkctl
output to havecilium_vxlan
to beunmanaged
instead ofconfiguring
. Also check that it fixes the mentioned issue with Stable 2905.2.0Testing done
Manually added the file to
/etc/systemd/network/
and verified that it fixed the reproducer and the kubeadm.cilium.base test and ran a full test http://localhost:9091/job/os/job/manifest/3158/cldsv/ for the commit here