Kilo not assigning the same wireguard ip to the nodes in the same mesh?

[Jonathan-Eid]

One of my three master nodes was assigned the wrong wireguard Ip, causing it not to be able to route traffic to the other nodes in a different mesh.

master-cluster-vm1:~# k exec -n kube-system kilo-cwt7n -- ifconfig kilo0
Defaulted container "kilo" out of: kilo, install-cni (init)
kilo0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.4.0.2 P-t-P:10.4.0.2 Mask:255.255.0.0
UP POINTOPOINT RUNNING NOARP MTU:1420 Metric:1
RX packets:44223648 errors:137 dropped:0 overruns:0 frame:137
TX packets:54593394 errors:0 dropped:226 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:19625855884 (18.2 GiB) TX bytes:47534617840 (44.2 GiB)

master-cluster-vm2:~# k exec -n kube-system kilo-cw4m2 -- ifconfig kilo0
Defaulted container "kilo" out of: kilo, install-cni (init)
kilo0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.4.0.2 P-t-P:10.4.0.2 Mask:255.255.0.0
POINTOPOINT NOARP MTU:1420 Metric:1
RX packets:572 errors:0 dropped:0 overruns:0 frame:0
TX packets:739 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:155392 (151.7 KiB) TX bytes:679140 (663.2 KiB

master-cluster-vm3~# k exec -n kube-system kilo-s9g9b -- ifconfig kilo0
Defaulted container "kilo" out of: kilo, install-cni (init)
kilo0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.4.0.1 P-t-P:10.4.0.1 Mask:255.255.0.0
POINTOPOINT NOARP MTU:1420 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Why does Master 3 have a different ip assigned when all three masters have the same location annotation?
kilo.squat.ai/location: gcp ?

Manually changing the ip of the kilo0 interface on master 3 solved my issue, but how come I had to manually change it in the first place?