<p>How does it work actually? When I start my Kubernetes cluster I can access the address <code>0.0.0.0</code> in my browser. When I create a LoadBalancer I can access some other address in my browser e.g. <code>174.23.0.12</code>. How does Kubernetes know that those addresses are not colliding with some other addresses? Is it possible to e.g. serve a react app on some IP like that?</p>

Likepineapple
<p>To my understanding, 0.0.0.0 is a non-standard broadcast address (according to <a href="https://datatracker.ietf.org/doc/html/rfc1122#page-66" rel="nofollow noreferrer">RFC 1122, section 3.3.6</a>) so your request to 0.0.0.0 is received by all hosts on your local network and the address is <em>not</em> routed, so it stays in your local network. You as client don't need to know the actual target address.</p>
