[ Kube 33.2 ] Deploy MetalLB in Kubernetes | Load Balancing solution

In this video, I will show you how to deploy and use MetalLB in your Kubnernetes cluster for load balancing solution.
MetalLB is a load-balancer implementation for bare metal Kubernetes clusters, using standard routing protocols.
Metallb:
metallb.universe.tf/
[ Kube 33 ] Set up MetalLB Load Balancing for Bare Metal Kubernetes
• [ Kube 33 ] Set up Met...
[ Kube 33.1 ] How to deploy & use MetalLB in bare metal Kubernetes
• [ Kube 33.1 ] How to d...
😺 Github:
github.com/justmeandopensourc...
📺 Learn Kubernetes Playlist:
• Learn Kubernetes
Hope you enjoyed this video. Please share it with your friends and don't forget to subscribe to my channel. For any questions/issues/feedback, please leave me a comment and I will be happy to help.
👏 Thanks for watching.
💗 If you wish to support me:
www.paypal.com/cgi-bin/webscr...

[@droit19]

For anyone out there, this is one of the best videos to deploy MetalLB on a Vagrant Kubernetes installation.

[@justmeandopensource]

Hi, Thanks for watching.

[@praveenkore842]

you are giving updates of older videos & explaining the things in most precise manner ...venkat take a bow ..we are so glad to have you..👌

[@justmeandopensource]

Glad to have your feedback. Thanks.

[@cryp2tsman699]

Hi Venkat, The beauty of what you do vs all other KZbinrs is that you act just in time to cover your previous posts which you made when it comes to changes (not caused by you but in this case Metallb released new version) that has domino effects on related playlist training . This is a noble approach that takes enormous efforts and passions to get this fixed, at the same time, caring about your audience.... This is priceless . Thanks

[@justmeandopensource]

Hi, I highly appreciate your effort in taking time to feedback. Thanks for your interest in my channel. Yes it takes lot of effort to keep up with technology updates. The videos unlike documentation can't be edited once uploaded and it becomes outdated soon these days. I am trying my best to keep them up to date by posting follow up videos. Partly I rely on viewers feedback to tell me something has changed which is when I look to do updated videos. Cheers.

[@pankajs5072]

Thanks, your tutorials are all to the point without any deviation.

[@justmeandopensource]

Hi Pankaj, thanks for your comment.

[@lespinoz]

Awesome job highlighting the differences! I was stocked at that point and you just helped me to resolve my issue! (Pool acknowledgment) - Awesome video!

[@justmeandopensource]

Hi Leiver, thanks for watching. Glad that you found this useful. Cheers.

[@hirenpatel2006]

Great Video concise and to the point. Keep it up

[@justmeandopensource]

Glad you liked it! Thanks for watching.

[@KrachaborasJB]

Thanks, today I tried to run metallb for the first time :) and saw that configurations is different for latest version in all youtube metallb videos, then BAM. You uploaded new video ! :D

[@justmeandopensource]

Many thanks for watching. Glad you found it useful. Cheers.

[@Christian-su2df]

Good job Venkat! Thank you again for your well-explained video!

[@justmeandopensource]

Thanks for watching.

[@canislupax]

Hey Venkat! Your Videos teached me so much. Thank you so much for sharing your knowledge.😊

[@justmeandopensource]

Hi Stefan, thats great to hear. Thanks for your interest in this channel.

[@amitpawar3859]

Thanks Venkat for the Video. Nice information on Metallb loadbalancer. I have watched your earlier videos on this topic. Thanks again for such a nice information.

[@justmeandopensource]

Thanks for watching Amit.

[@inversemetric]

Thanks for keeping your content fresh and relevant, you've saved me a lot of hassle!

[@justmeandopensource]

No worries. Thanks for watching.

[@suhasraj9054]

Hi Venkat , Your explanations are very clear and as for as i know ...you are the only person on KZbin to make so many vedios ok kubernetes to explain almost all concepts of k8..Thanks for all the effort ✨

[@justmeandopensource]

Hi Suhas, many thanks for watching. Cheers.

[@sakshamconsul1389]

Very useful. Thank you for sharing such content

[@justmeandopensource]

Glad it was helpful! Thanks for watching.

[@DevinFlake]

These updated videos are much appreciated! :)

[@justmeandopensource]

Hi Devin, thanks for watching.

[@justmeandopensource]

Thanks

[@VuvaToniKroos]

I really appreciate what you did.

[@justmeandopensource]

Thanks for watching.

[@mosespeter9711]

Thanks so much for this... I wish I have seen you earlier

[@justmeandopensource]

Thanks Moses.

[@rsrini7]

Venkat .. Amazing... Thanks..

[@justmeandopensource]

Hi Srini, Thanks for watching.

[@kriswachtell]

thank you so much for your great vids. You teach me so much!

[@justmeandopensource]

Hi, Thanks for watching.

[@kriswachtell]

@@justmeandopensource BTW the pod security policy warning has been fixed by Metallb

[@justmeandopensource]

Cool. Good to know. Thanks.

[@kriswachtell]

@@justmeandopensource All the UFW in the kubernetes cluster are disabled. However, I have an issue where I can ping the first IP in the IPaddresspool and also curl and get the nginx welcome page from inside one of the master or worker nodes but not from the workstation on the LAN. I suspect that this is to be expected, but do you know how I can disable the feature in Metallb so I can reach the from other members on the LAN?

[@markdabasol6707]

The best!

[@justmeandopensource]

Hi Mark, thanks for watching.

[@v9tech]

welcome back.

[@justmeandopensource]

Thanks

[@pain1737_6]

Thanks bro

[@justmeandopensource]

You are welcome. Thanks for watching.

[@pain1737_6]

@@justmeandopensource I have a question for you. Do you have any your paid courses about kubernetes?

[@justmeandopensource]

@@pain1737_6 No. Just the ones you see in KZbin.

[@pain1737_6]

@@justmeandopensource Hi bro, thanks to you I set up a kubernetes cluster. I'm using flannel for networking. When I set up metallb with two IP addresses - 192.168.63.6/32 and 192.168.63.7/32 - the ingress controller service chose the first one and then I applied the own ingress for the project! Everything is fine, it works correctly. But there is a question, if something happens to the server 192.168.63.6, users cannot connect to our project, is there any option to deploy ingress between clusters, I mean like deployment, how they work synchronously with each other or like if something happens so that ingress would still work EDIT: oh shit bro so sorry, now i figured out how actually ingress works. It was stupid question x)

[@fedefede843]

Hi Thanks for the video! 2 things, first one BGP setup would be really nice to see, and number two, which CNI are you using? I read Calico might have issues with Layer 2 approach??? Cheers!

[@najibiziki4070]

I have a question about deploy mongodb statefulset. you mentioned at the end of the video that there is a method to make rs.add() dynamic when scaling k8s sts, without going back to each see and scaling mongodb rs manually. thank you in advance

[@tadeubernacchi3360]

Nice video. That's sound amazing. Quick question...installing MetalLB I don't need a ingress controller? I"m trying to setup an ExternalIP for my services on DigitalOceanI have a RKE2 cluster int there I don't want to use their LoadBalancer. With this procedure will work? Thanks!

[@nareshpandian1321]

Hey Venkat, Do we have a doc reference or vide for a kubeadm cluster with loadbalancer support (basically external public ip ) ?

[@amitchettri_ac]

Hi Venkat. Thanks for uploading this video. It very informative. I was wonder if you have the active slack or mail Id for faster interaction

[@justmeandopensource]

Hi Amit, thanks for watching. I can reply in KZbin comments section. That is the best way to contact me. Cheers.

[@edtix]

Hi Venkat, Love your videos! What is better for preproduction cluster metallb or just ingress on node port? Metallb is super convenient but I worry it's not as stable as ingress on nodeport.

[@justmeandopensource]

Hi Ed, thanks for watching. I haven't used MetalLB in production/preproduction. Not sure about the stability of it though. Ingress via node port is an option but not elegant. kube-vip is another promising alternative for metallb. I haven't tried it though.

[@openshores4288]

You can use both. deploy metallb then deploy nginx-ingress as LoadBalancer (if you have ingress in your deployments)..

[@telloasem]

hey great video, question from me... in real case scenario where do you get those ip addresses pool? are those public ip the we need to assign to our servers? sorry newbie question

[@MohammedNoureldin]

Thanks for this update! Shouldn't the IP address range in Metallb be a public IP (accessible from outside) to be assigned to the Load Balancer? Or how will the load balancer be the first entrypoint for the requests?

[@openshores4288]

yes, it should be a public ip

[@dougsellner9353]

NO! - they should be internal IPs, and your router/firewall that connects to the internet should route 80,443 (and other needed ports) to this IP. (port forwarding)

[@gencaypolat8901]

Firstly thank you so much for the guide. I have one issue. I get the nginx welcome page from the terminal but can't from the browser. I used Ubuntu 20.04 which I created on Google Cloud Platform. How can I overcome this issue?

[@ranjeetbadhe]

I have got 3 worker nodes , I install MetalLB but how to get the load balanced across the pods on worker nodes ? Or load balancing within cluster across the worker nodes will be taken care by service? I am confused please help.

[@phalla6646]

Hi Venkat, Thank for the video, it is clear and easy to catch up. I have a question. Can we use metallb in production environment? Is it reliable?

[@justmeandopensource]

Hi Phalla, thanks for watching. I haven't used it in production. But to me, it just works fine.

[@phalla6646]

Thank for your input

[@justmeandopensource]

@@phalla6646 You are welcome.

[@habesha2663]

I configured same way but the LB external IP is not accessible from outside of cluster. But I do access nginx within the cluster for instance the nodes. Is this expected ?

[@Anonymous2026]

Hi Venkat, I have setup metallb in my kubeadm cluster, but I am getting no response when I try to curl it.

[@dpicollege]

ok i have external ip and can curl for my nginx but i cant's access to nginx from outside of cluster node!!!! i mean a pc on same range ip network but outside of cluster any idea? i deploy my cluster on local network.

[@krunal4baps]

Hi, I have pfsense router at home and K8S bare metal running on ubuntu with 2 master 2 worker setup.. I configured BGP on pfsense and I am hoping it's good, the logs are showing the assigned LoadBalancer IPs but somehow I can't resolve them on browser... I tried multiple times but something somewhere missing, any clue where should I be looking at? I have External IPs assigned correctly on get service output and on pfsense. It does show external ip in BGP logs that the next hop if worker nodes but when I put them in browser, it's bad gateway!!

[@amrhegazy7221]

thanks vankat, can we use another software rather than metallb for local kubernetes ?

[@justmeandopensource]

I have only tried Metallb so far as it works fine for my needs. But there are others as well like kube-vip which I haven't tried yet.

[@BaBuBank]

Hello Venkat, Can you please share your pc/laptop spec and your Linux configs ? Do you use touchpad on the laptop ? Do you remap the ctrl key to copy paste ?

[@justmeandopensource]

Hi, I use Dell XPS 13 9310 - 16G RAM - 8 CPU Intel 11th Gen Processor. As for Linux configs, I use NixOS as my operating system and the dotfiles/config files are all in the below repo github.com/justmeandopensource/nixos-dotfiles

[@hodolomax]

Hi Venkat, can you explain how to update older running metallb installation to latest version in this video? thanks

[@Ironoy99]

try metallb's new configmaptocrs tool

[@justmeandopensource]

Thanks for the pointer. I am going to try that. Cheers.

[@pjj7466]

Hello sir, I have tried the same and exposed a sample nginx deployment with a service as a load balancer. Unfortunately, when I hit the IP address of the load balancer for my nginx sample service, I am able to get a response and it's working fine within the cluster, but when I try to access the same IP address from my browser, it doesn't connect. Can you please help me with this issue?

[@hackerops1407]

One question here venkat if I take 3 instance on aws and crate kubeadm cluster and after that try on that it will work or not because I see in video you are saying this will not work on cloud

[@justmeandopensource]

I am inclined to say that it won't work but I haven't tried.

[@hackerops1407]

Ok venkat I'll try tomorrow and let you know I think its should be work because at the end I am creating kubeadm cluster and try lots of time to take lb SVC but it will go in pending so might be it will work Thanks for replying 👍

[@justmeandopensource]

@@hackerops1407 No worries. Interested to know whether it works.

[@hackerops1407]

Hello venkat just wanted to confirm that I have do poc now on aws take 2 instance create kubeadm cluster and follow metllb docs and it's working fine thanks for the good session 👌

[@mshanmukhanathreddy464]

Hi, i have deployed the metallb, i got the external IP( which is in range of my node's internal network) But, does this work like an actual public IP address? because it's not working when i hit the IP on browser.

[@justmeandopensource]

It should work and thats the concept.

[@mshanmukhanathreddy464]

@@justmeandopensource Well, it worked on externalip:nodeport not on port 80, on the browser..

[@gencaypolat8901]

I'm experiencing the same issue as well. Have you solved it, if you have, could you explain how?

[@Komradenter]

Year leter...new updated video? :))

[@justmeandopensource]

Thanks for watching. Let me find some time to do it. Cheers.

[@Komradenter]

thanks for great job@@justmeandopensource

[@nandakishore3492]

Your content is not working 😜

[@ameyas4268]

kubernetes 1.25 vagrant flannel metallb 0.13.5 error when creating "metallb-config_yaml": Internal error occurred: failed calling webhook "ipaddresspoolvalidationwebhook_metallb_io": failed to call webhook: Post "webhook-service.metallb-system_svc_443/validate-metallb-io-v1beta1-ipaddresspool?timeout=10s": context deadline exceeded got above issue with flannel working with calico p.s have added underscore to avoid comment being removed

[@paulhakh6038]

Same issue. Did you solve it?

[@adhitya10]

I don't know if you have solve this problem and I don't know the one that I want to share is the right one. But what I did is to delete the webhook and the rest will work nicely. Just run kubectl delete -A ValidatingWebhookConfiguration ipaddresspoolvalidationwebhook_metallb_io