<p>I am trying to set up a metalLB external load balancer with the intention to access an nginx pod from outside the cluster using a publicly browseable IP address. I have follwed all the steps provided in <a href="https://www.youtube.com/watch?v=xYiYIjlAgHY" rel="nofollow noreferrer">here</a>. I have managed to get the External-IP for service/nginx type:LoadBalancer, but when I try to browse the IP address, I get nothing and it says &quot;This site can’t be reached&quot;.</p>
<p><a href="https://i.stack.imgur.com/SltRK.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/SltRK.png" alt="running kubectl get nodes -o wide shows" /></a></p>
<p><a href="https://i.stack.imgur.com/CwsnY.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CwsnY.png" alt="enter image description here" /></a></p>
<p>I wonder whether is it even allowed on the docker-desktop win10 environment to access the k8s cluster resources from outside with a public IP address?</p>

<p>Kuberntes provided by Docker Desktop is running in a VM and all network traffic is being NATed to a virtual machine. Even if you had everything properly configured on your network for using layer 2 and DHCP, your work or home router would not even know how to reach Docker which makes any services only available on the localhost. </p>

<p>To make it work you coud try using minikube with VirtualBox driver and set network interface to bridge, so that the minikube VM is visible to your router as a standalone instance and therefore arp requests can reach minikube.</p>
