A short booth session at the Isovalent booth during KubeCon + CloudNativeCon Europe 2026.
Abstract
You deploy a LoadBalancer service on a bare-metal cluster, it gets an external IP, and nothing outside the cluster can reach it. Cloud providers hide this problem from you. On-premises, a LoadBalancer service IP means nothing until something on the L2 network claims it.
This session explains how address resolution works for service IPs (ARP for IPv4, NDP for IPv6), and how Cilium L2 Announcements use leader election to pick a node that claims the IP and answers resolution requests, with no external load balancer needed.