Multi-Homed Spine-Leaf Kubernetes

Sun, 08 Feb 2026 00:00:00 +0000

Overview

In my pursuit to learn more and migrate my existing Proxmox-based infrastructure to Kubernetes, I faced the issue of physical redundancy. While having three nodes does provide failover there are still other single points of failure, primarily my physical network topology. I have previously been able to work with L2 RSTP in Proxmox using Open vSwitch to add redundancy as well as mixing and prioritizing network port speeds. Talos Linux and Cilium did not seem willing to participate in RSTP, so I needed to resort to other methods, Link Aggregation was my next approach. But I was quickly dissuaded by LACP’s inability to bond ports of unlike speed and Cilium’s eBPF binding to the raw interface instead of the virtual Bond. The next idea on the list that I could think of was a full Layer3 Routed Spine-Leaf topology setup.

Custom IPv6 Dashboard

Thu, 27 Nov 2025 00:00:00 +0000

LibreNMS + Custom IPv6 Client Dashboard

The Problem

The Network monitoring solutions that I have seen seem to be stuck in the past with IPv4 only networks, seemingly relying on ARP and Nmap scans of network blocks to find devices and services on the network. From what I have heard, a single IPv6 Subnet with a /64 prefix has some 18 quintillion Addresses. That does not include the extra 64 thousand other subnets in the /48 that likely is assigned to location

Mikrotik on Thomas Peters

Multi-Homed Spine-Leaf Kubernetes

Overview

Custom IPv6 Dashboard

LibreNMS + Custom IPv6 Client Dashboard

The Problem