Has anyone used #LoxiLB? It looks interesting.
I wonder if it can run side by side with #MetalLB without clashing.
#K8S

ugh seriously
I provisioned a network vlan 10, 192.168.10.0/24.

I can arping the provisioned LB ip just fine.

I'm running on esxi/vSphere 7 dSwitch.

I see the IP request for port 80 in tcpdump.

I SEE THE LOAD BALANCER IP AND MAC ADDRESS OF THE k8S NODE IN THE LIST OF CONNECTED CLIENT ON THE NETWORK!

BUT YOU CAN'T ROUTE TO IT!?

#kubernetes #MetalLB #DreamMachinePro #Ubiquiti

While preparing for my @\KcdTurkey talk, I tried again #MetalLB, which didn't work previously, probably because of the additional VM layer on Mac.

Today, it works. I'll be able to speak (briefly) about the LoadBalancer object 😊

I got metallb and cilium working, and traefik seems to be a piece of cake

#metalLB #cilium #traefik #kubernetes #talos

Configuring #routing for #MetalLB in L2 mode | by Andrei Kvapil | ITNEXT https://itnext.io/configuring-routing-for-metallb-in-l2-mode-7ea26e19219e

#Kubernetes

New #blog post: moving my home cluster to #k3s 🙂

https://yolops.net/k3s-at-home.html

#k8s #kubernetes #cilium #ipv6 #MetalLb #SelfHosting

I've updated my guide on using #metallb on bare-metal #kubernetes, to include the recent migration to CRDs (thanks @MegaShinySnivy for reminding me!) : https://geek-cookbook.funkypenguin.co.nz/kubernetes/loadbalancer/metallb/

everything is on the k8s cluster. all the raspberry pis are _powered off_. holy shit :blobfoxwhoaa:

now that the migration is complete, it's time to write a blog post!

#unifi → #sidero → #k8s → #metallb → #traefik → $SERVICE

#homelab

Ahh, good old metalLB issues, but this time it's a PEBKAC. Need to update to MetalLB 4.X, but they introduced a major breaking change with how metalLB is managed (going from a ConfigMap to using CRDs) and I, being my supremely lazy self, have yet to actually work up the give-a-damn to update. All this said to say, stop guilt-tripping me renovate-bot i know things are out of date 😢

#kubernetes #gitops #metallb #homelab

I wish long life for my old HP Z420 workstation. It runs the #homelab #Kubernetes dev cluster on HA mode. It can also run OpenShift-local. Powered by #Fedora 37 and #KVM.

- #kubespray
- #metallb
- #longhorn
- #kubegres

I wish long life for my old HP Z420 workstation. It runs the #homelab #Kubernetes dev cluster on HA mode. It can also run OpenShift-local. Powered by #Fedora 37 and #KVM.

- #kubespray
- #metallb
- #longhorn
- #kubegres

Okay, so let me tell you about my doorbell, from a #networking perspective.

When you push the button by the door, it sends a message over the #zigbee wireless mesh network in my house. It probably goes through a few hops, getting relayed along the way by the various Zigbee light switches and "smart outlets" I have.

Once it makes it to my utility closet, it's received by a Zigbee-to-USB dongle, through a USB hub (a simple tree network) plugged into an SFF PC. From there, it gets fed into zigbee2mqtt, which, as the name implies, publishes it to my local #mqtt broker.

The mqtt broker is in the small #kubernetes cluster of #raspberrypi nodes I run in my utility closet. To get in (via a couple of #ethernet switch hops), it goes through #metallb, which is basically a proxy-ARP type service that advertises the IP address for the mqtt endpoint to the rest of my network, then passes the traffic to the appropriate container via a #linux veth device.

I have #HomeAssistant, running in the same Kubernetes cluster, subscribed to these events. Within Kubernetes, the message goes through the CNI plugin that I use, #flannel. If the message has to pass between hosts, Flannel encapsulates it in VXLAN, so that it can be directed to the correct veth on the destination host.

Because I like #NodeRed for automation tasks more than HomeAssistant, your press of the doorbell takes another hop within the Kubernetes cluster (via a REST call) so that NodeRed can decide whether it's within the time of day I want the doorbell to ring, etc. If we're all good, NodeRed publishes an mqtt message (more VXLANs, veths, etc.)

(Oh and it also sends a notification to my phone, which means another trip through the HomeAssistant container, and leaving my home network involves another soup of acronyms including VLANs, PoE, QoS, PPPoE, NAT or IPv6, DoH, and GPON. And maybe it goes over 5G depending on where my phone is.)

Of course something's got to actually make the "ding dong" sound, and that's another Raspberry Pi that sits on top of my grandmother clock. So to get *there* the message hops through a couple Ethernet switches and my home WiFi, where it gets received by a little custom daemon I wrote that plays the sound via an attached #HiFiBerry board. Oh but wait! We're not quite done with networking, because the sound gets played through PulseAudio, which is done through a UNIX domain socket.

SO ANYWAY, that's why my doorbell rarely works and why you've been standing outside in the snow for five minutes.

Grr. Time to reinstall MetalLB in BGP mode, for some reason one of my nodes just gives the fheck up and refuses to communicate with the rest of the cluster metalLB-wise.

#kubernetes #metallb #homelab

Finally, I got a working dual-stack K3s mononode cluster, this time using Cilium as a CNI.
(as I should have done from the start)

NDP passthrough is now working as it should, pods get direct connectivity using their own #ipv6, no NAT or other blasphemous behavior involved.

So I think that my next server at home will run #k3s, using the same network/services stack as my previous #k8s 3-nodes cluster:
- #Cilium
- #MetalLb
- ingress #nginx

Same thing, but lighter, and on a single node.

Is it possible to put a #MetalLB load balancer or #Traefik in front of #kubernetes API service ie so if you have multiple master nodes, it balances? I can't figure out what the correct way to do it is.