Local IPs with Robots server on vSwitch not working

[mglants]

TL;DR

Node not adding if kubelet IP is set to internal network via Vswitch

Expected behavior

Node succesfully updated with Node controller

Observed behavior

Node broken and stays as uninitialized

Minimal working example

No response

Log output

E0702 15:17:50.125761       1 node_controller.go:240] error syncing 'kn2-stage.htzn': failed to get node modifiers from cloud provider: provided node ip for node "kn2-stage.htzn" is not valid: failed to get node address from cloud provider that matches ip: 192.168.0.131, requeuing
I0702 15:17:50.135997       1 node_controller.go:431] Initializing node kn2-stage.htzn with cloud provider

Additional information

NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME km1-stage Ready control-plane 14d v1.27.2 192.168.0.3 Talos (v1.7.0) 6.6.28-talos containerd://1.7.15 km2-stage Ready control-plane 14d v1.27.2 192.168.0.5 Talos (v1.7.0) 6.6.28-talos containerd://1.7.15 km3-stage Ready control-plane 18d v1.27.2 192.168.0.4 Talos (v1.7.0) 6.6.28-talos containerd://1.7.15 kn1-stage.htzn Ready 155m v1.27.2 192.168.0.130 Talos (v1.7.4) 6.6.32-talos containerd://1.7.16 kn2-stage Ready egress-proxy 13d v1.27.2 192.168.0.131 Talos (v1.7.4) 6.6.32-talos containerd://1.7.16

[apricote]

Hey @mglants,

using IPs assigned through the vSwitch is not supported right now. We only support Private Networks in Cloud-only clusters.

[mglants]

solved with specify hrobot id if in every node