This message was deleted.

Not clear what u want to achieve. let cilium replace Klipper for LoadBalancer ? This require bgp or l2 config (equivalent of metallb L2). https://docs.cilium.io/en/latest/network/l2-announcements/

I read further and get the concept little better at the moment. ServiceLB watches for loadbalancers to assign the IP. In this case its nodes IP. What i coudlnt find how to assign nodes IP with cilium LB IPAM. For expose of ports, i think i will need network policies for that since cilium wont do it like service LB did i think.

Yes ServiceLB = Klipper. Uses NodeIP as LoadBalancer IP. Thats k3s specific. If you need genuine / external IP on premise, must use Metallb or Cilium

I will use cilium. I see i can achieve it with l2 + lb ipam. But in this case i need a new network block(the one i assign on lb ipam that get by traefik as externaip.) that is routable on nodes LAN. If i get the idea correctly.