Kubernetes on Thomas Peters

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.

Website Reboot: Now on Self-Hosted Kubernetes!

Tue, 11 Nov 2025 00:00:00 +0000

Welcome back! The blog is getting a fresh start, and this time it’s powered by self-hosted Kubernetes.

After some time away, I’ve decided to reboot the blog with a new infrastructure approach. Rather than relying on traditional hosting or managed services, I’ve moved everything to a self-hosted Kubernetes cluster. This gives me complete control over the deployment pipeline, scaling, and infrastructure management.

What’s New

Self-Hosted Kubernetes: Running on my own hardware, giving me full control over the entire stack
Modern CI/CD: Automated deployments with proper containerization
Infrastructure as Code: Everything version controlled and reproducible

Stay tuned for more posts about the technical details of the setup, lessons learned, and future projects. The blog is back and ready to go!