Use MetalLB to provision External IP for LoadBalancer service on Kind Kubernetes cluster

[@Intaberna986]

Great presentation, thanks very much.

[@mrbharatmehta]

Good work. Thanks for sharing

[@aloispetutschnig8342]

Also works perfectly fine with Cilium LoadBalancer and L2 Announcement

[@shoibericsson5007]

Nice explanation 😊 Could you please show BGP advertisement as well !

[@AmalChandran-k8v]

Thanks for the on point & simple explanations

[@mxmclr]

You must assign an IP range from your local network to use as DHCP in MetalLB ; otherwise there will be no way to contact that kubernetes service on your network.

[@conradtaylor29]

I have tried it with Orbstack and Docker Desktop but it only works with OrbStack. From what I have learned, Docker Desktop doesn't expose IP addresses from its Linux VM to the host OS (i.e. macOS).

[@ConcerninglyWiseAlligator]

Yeah, and it's the same on windows. Even the Kind documentation addresses with a: "If you are using Docker Desktop, tough luck... But here is the Extra Port Mappeings feature so you can at least curl localhost:[LoadBalancer NodePort]" And Minikube also complains about Docker Desktop everytime you fire up a cluster.

[@juanmarioparra]

Excuse my ignorance but where does the kind network come from?

[@Nutricare-yr3fe]

Why do you used docker network ? I don't understand.

[@ctroyp]

Very well explained

[@Wesley34927]

Very Nice. Thanks for sharing

[@aloispetutschnig8342]

Thanks man!

[@akashshinde3522]

can't access it on the browser

[@9966989500]

You explained just like that with an ease... | this is the best part.

[@akumpum]

Hello, with adresses 172.18.0.100-172.18.0.110 the LoadBalancer take the ip 172.18.0.100 and the curl is working, I can reach the app. If i tried to change the mettlb config with: addresses: - 192.168.1.100-192.168.1.110 The LoadBalancer take the externalIP: 192.168.1.100, but the curl fail. The IP of the host where kind cluster is running is: 192.168.1.11 Any idea ? thanks

[@jean-baptistelasselle4562]

Idk if any of guys get smae than me, but me, if i deploy the metallb using the helm helm chart, with all defaults values, just like Li Yang (thks for th video), I get this : ~$ kubectl get cm -n metallb-system NAME DATA AGE kube-root-ca.crt 1 42m metallb-excludel2 1 43m metallb-frr-startup 3 43m And there its configured a way i didnt expect, yet,THANK YOU SO MUCH LI YANG, because now it does work!! (it's been months that i was searching for a working tutorial to have metallb working on a bare metal deployement!) : ~$ kubectl get all NAME READY STATUS RESTARTS AGE pod/hello-server-77f56f7674-n7bmv 0/1 ImagePullBackOff 0 47m pod/nginx-7c5ddbdf54-c4fqv 1/1 Running 0 5s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10.96.0.1 443/TCP 47m service/nginx LoadBalancer 10.96.135.62 172.19.0.240 80:30775/TCP 5s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/hello-server 0/1 1 0 47m deployment.apps/nginx 1/1 1 1 5s I curl 172.19.0.240 from the docker host and its working soooo welll just as expected, thanks so much LI YANG!