K3s fails to start in a multi-network card environment with error "IPv6 was enabled but no IPv6 address was found on node" about k3s HOT 7 CLOSED

Could you try with a newer version of k3s? I have just tried K3s with v1.29.3 and it was starting even if flannel was using one interface and I was defining the IPs of another interface in node-ip

from k3s.

Do I understand correctly that you are changing the node-ip and flannel-iface settings on an existing node? If so, you will likely have to temporarily start k3s with --disable-network-policy so that the node can start up and update the node addresses to add the IPv6 address. Once that is done you can re-enable network policy.

@manuelbuil this seems to come up again from time to time, do you think we could perhaps get the netpol controller startup to retry, or wait until after the node addresses have been synced?

from k3s.

@brandond Thank you for your reply. My scenario is a new installation, not changing the network card for an already installed k3s environment. My problem is, if the Linux system has two network cards A and B, while A is the network card used by the default route, if the ipv4 and ipv6 configurations of A are given to k3s for installation, k3s can be installed successfully. But if the ipv4 and ipv6 addresses of B are configured for k3s installation, the installation will fail, indicating that "IPv6 was enabled but no IPv6 address was found on node".

from k3s.

There is a configuration parameter flannel-iface, is it helpful to you?

from k3s.

@bingfengfeifei I used this parameter --flannel-iface to specify the network card name B, and the --node-ip parameter in k3s is also configured with the ipv4 and ipv6 addresses of this network card B( B is network card which not used by default routing rule) to install k3s, but k3s still reports "IPv6 was enabled but no IPv6 address was found on node".
It seems that k3s cannot start using a network card that does not used by the default routing rule.

from k3s.

Good catch; 1.27.1 is fairly old at this point. Closing this out but can reopen if this can be reproduced on the latest release.

from k3s.

Could you try with a newer version of k3s? I have just tried K3s with v1.29.3 and it was starting even if flannel was using one interface and I was defining the IPs of another interface in node-ip

tks，update k3s version to v1.29.4 can work！

from k3s.