Very challenging and inspiring illustration on the different service types of k8s! This is the most in-depth and advanced example I’ve seen so far on RUclips. Thx!
Hi Filip, I have followed along the instruction you have prepared here, and, before that - to create the cluster. I have one question regarding the external visibility of the Load Balancer using the MetalLB. Not sure if I have missed any step or is it because of my specific set up (I have built three VM's on VMWare which are on the NAT network on top of which I have built the master node and two workers), but when I have created the address pool and the L2 advertisement, it showed up in the cluster's services, however, it was not accessible externally. This was until I have added the IP assigned from the pool into the /etc/Netplan - I could see that earlier in the film you did this to one of the other external IP's. Is the IP not accessible because I did something wrong in the process, or is it an additional step that is necessary to expose the IP to the outside of the cluster ?
Hi! Once you create IPAddressPool and L2Advertisement, you should not have to modify your interface configuration. Whole point of MetalLB is that it should automatically respond to ARP packets. Make sure the IP Address Pool is from the same subnet, so if your external network is 192.168.10.0/24 then range could be a subset for example 192.168.10.100-192.168.10.200. Create a service of type Load Balancer and check the speaker logs (just go to the speaker pod and check it's logs). Follow steps from metallb.universe.tf/troubleshooting/ that is arping and tcpdump -n -i ens3 arp src host 192.168.1.240 etc.
18:07 I am getting error here >>>Error from server (InternalError): error when creating "ipaddresspool.yml": Internal error occurred: failed calling webhook "ipaddresspoolvalidationwebhook.metallb.io": failed to call webhook: Post "metallb-webhook-service.metallb-system.svc:443/validate-metallb-io-v1beta1-ipaddresspool?timeout=10s": context deadline exceeded .....please advise how to fix it
Hi Any chance to make a video on wireguard how to make a WG VPN Chain? That is when a client to reach internet would go thru multiple WG tunnels. Client1 (laptop) > node1 > node2 > gateway > internet i was able to only create 1 node in between laptop and internet (standard vpn). thanx!! By the way, great video, liked and subscribed!!!
Very challenging and inspiring illustration on the different service types of k8s! This is the most in-depth and advanced example I’ve seen so far on RUclips. Thx!
Glad it was helpful! Please stay tuned for more interesting content! Cheers!
This is very well made. Thanks for sharing.
Glad you enjoyed it! Thanks!
Excellent 👍
Thank you! Cheers!
Thanks , great elaboration !
Glad it helped!
we are indeed interested in how the cluster was built
Got it! Will prepare a video about it.
ruclips.net/video/96mqy5iCjoA/видео.htmlsi=G0H0JtEBhVKaNkyi
Hi Filip, I have followed along the instruction you have prepared here, and, before that - to create the cluster. I have one question regarding the external visibility of the Load Balancer using the MetalLB. Not sure if I have missed any step or is it because of my specific set up (I have built three VM's on VMWare which are on the NAT network on top of which I have built the master node and two workers), but when I have created the address pool and the L2 advertisement, it showed up in the cluster's services, however, it was not accessible externally. This was until I have added the IP assigned from the pool into the /etc/Netplan - I could see that earlier in the film you did this to one of the other external IP's. Is the IP not accessible because I did something wrong in the process, or is it an additional step that is necessary to expose the IP to the outside of the cluster ?
Hi! Once you create IPAddressPool and L2Advertisement, you should not have to modify your interface configuration. Whole point of MetalLB is that it should automatically respond to ARP packets. Make sure the IP Address Pool is from the same subnet, so if your external network is 192.168.10.0/24 then range could be a subset for example 192.168.10.100-192.168.10.200. Create a service of type Load Balancer and check the speaker logs (just go to the speaker pod and check it's logs). Follow steps from metallb.universe.tf/troubleshooting/ that is arping and tcpdump -n -i ens3 arp src host 192.168.1.240 etc.
@@LinuxCloudHacks Many thanks. I'll give it a go
great content, installation process that can be sharded would be greatly appreciated
Coming soon!
18:07 I am getting error here >>>Error from server (InternalError): error when creating "ipaddresspool.yml": Internal error occurred: failed calling webhook "ipaddresspoolvalidationwebhook.metallb.io": failed to call webhook: Post "metallb-webhook-service.metallb-system.svc:443/validate-metallb-io-v1beta1-ipaddresspool?timeout=10s": context deadline exceeded
.....please advise how to fix it
Hi, this is a self build kubernetes cluster? (which version) or it's k3s or minikube etc? I'll need to reproduce it.
is there any git profile where to find these files and explanations ?
one of my favorites youtube channels.
Thanks! I need to start github. Apologies :(
thank you :)
You're welcome! Thanks for the visit.
Can you kindly put something with BGP in conjunction with pfsense router? I have it external ips assigned but it doesn't resolve at all...
Now we are talking! I was planning to release one with BIRD2 or Mikrotik as the BGP layer. I'll definitely prepare something. Stay tuned.
@@LinuxCloudHacks thanks so much!
Hi
Any chance to make a video on wireguard how to make a WG VPN Chain?
That is when a client to reach internet would go thru multiple WG tunnels.
Client1 (laptop) > node1 > node2 > gateway > internet
i was able to only create 1 node in between laptop and internet (standard vpn).
thanx!!
By the way, great video, liked and subscribed!!!
Thanks! And will do!
Your demos are too fast, difficult to follow.
I appreciate the feedback. I'll work on making the demos easier to follow. If you're still having trouble, feel free to ask questions in the comments.