In our case, we rent a lot of dedicated servers from various hosting providers, and they provide the ability to set up an LACP bond, but after that, it's not possible to automatically provision Talos nodes because the hosting provider's switches discard ports and reject packets until the LACP bond is configured on Talos side.
As a workaround, I have to generate an ISO on https://factory.talos.dev with the following configuration:
So, basically, I disable predictable network names and try to configure the LACP bond using the first 4 (or more) network interfaces.
After installing Talos, I have to reboot the machine and manually remove net.ifnames=0 from kernel args in the GRUB menu; after that, I do talosctl upgrade to save this change. For some reason, deleting net.ifnames=0 from the kernel args doesn't work when using -net.ifnames in the machineconfig.
It would be better to provide some way to configure the LACP bond on all physical network interfaces using kernel args since we have this selector in Talos 1.7:
In our case, we rent a lot of dedicated servers from various hosting providers, and they provide the ability to set up an LACP bond, but after that, it's not possible to automatically provision Talos nodes because the hosting provider's switches discard ports and reject packets until the LACP bond is configured on Talos side.
As a workaround, I have to generate an ISO on https://factory.talos.dev with the following configuration:
So, basically, I disable predictable network names and try to configure the LACP bond using the first 4 (or more) network interfaces. After installing Talos, I have to reboot the machine and manually remove
net.ifnames=0
from kernel args in the GRUB menu; after that, I dotalosctl upgrade
to save this change. For some reason, deletingnet.ifnames=0
from the kernel args doesn't work when using-net.ifnames
in the machineconfig.It would be better to provide some way to configure the LACP bond on all physical network interfaces using kernel args since we have this selector in Talos 1.7: