CPLB continue to add CPLB IP as etcd.peerAddress about k0s HOT 4 CLOSED

I think the issue is that my primary network interface has two IPs due to the CPLB?

That smells like it's the problem, yes. The original PR just skipped the dummy interface and didn't take into account that the virtual IP could be attached to a different interface, as well. Still not sure why k0s chose the second address. The assumption was that Go's net.Interfaces() returns interfaces and addresses in the "operating system's order". K0s picks the first non-loopback address, which should have been .5. 🤔

A proper fix would be to exclude/blacklist VRRP IPs when determining the address. The code is currently structured in a way that makes make this difficult. On the other hand, k0s should probably also prefer the primary (i.e. non-secondary) address of an interface. That's self-contained and should be enough to fix this issue.

from k0s.

Hi, this is indeed wrong.
Can you please provide the output of k0s etcd member-list as well?

from k0s.

Sure!

root@node1:~# k0s etcd member-list
{"members":{"node1":"https://192.168.0.5:2380"}}

from k0s.

The issue is marked as stale since no activity has been recorded in 30 days

from k0s.