There Has Been a Slight Change with My Lab: An Upgrade

๐Ÿ”ง My Reasoning for the Upgrade

Running Kubernetes on a single machine was a great way to get started. It was easy to manage, simple to test deployments, and perfect for learning. But over time, I ran into several limitations.

With just one node, I couldnโ€™t truly explore:

  • ๐Ÿ” Scheduling across multiple nodes
  • ๐Ÿ›ฐ๏ธ Cluster communication and service discovery
  • โš™๏ธ High Availability (HA) deployments
  • ๐Ÿ”ฅ Disaster recovery scenarios
  • ๐Ÿ“ˆ Horizontal scaling and load balancing

๐Ÿ’ธ The Upgrade

I decided to invest in a few low-cost Mini PCs to build out a proper cluster. I found a great option on Amazon: the OUMAX Mini PC. These are currently priced at just $141.54 USD.

They offer a solid set of specs for a home lab:

  • ๐Ÿง  CPU: Intel N150 (4 cores, 4 threads)
  • ๐Ÿ’พ RAM: 16GB
  • ๐Ÿ“ฆ Storage: 500GB NVMe SSD
  • ๐ŸŒ Networking: 2 x 2.5GbE NICs

๐Ÿ—๏ธ The New Lab Design

With three of these units, Iโ€™m now running a multi-node Kubernetes cluster where each node acts as both a control plane and a worker. The dual NICs let me physically separate:

  • ๐Ÿ”’ Internal traffic: cluster and storage communications
  • ๐ŸŒ External traffic: ingress/egress to the internet

This setup allows me to:

  • ๐Ÿ”„ Simulate node failure and recovery
  • ๐Ÿ› ๏ธ Add/remove nodes dynamically
  • ๐Ÿ“ก Test longhorn and NFS over an isolated backend network
  • ๐Ÿ“Š Analyze service behavior under load

๐Ÿ–ฅ๏ธ What About the Old Machine?

The original system isnโ€™t going away. Iโ€™ll be dedicating it to GPU-related workloads. Itโ€™s perfect for testing things like:

  • ๐Ÿง  AI models with the NVIDIA toolkit
  • ๐ŸŽฅ Media workloads like transcoding and inference

๐Ÿงช Whatโ€™s Next?

Iโ€™m considering picking up a fourth Mini PC and running Windows Server 2019/2022 on it. This would let me experiment with Windows containers and hybrid clusters.

๐Ÿ’ก I know Microsoft recommends Azure or Azure Stack HCI for Windows-based pods, but Iโ€™m curious to see whatโ€™s possible in a pure local setup. Even if itโ€™s not ideal, the experience alone will be valuable.

๐Ÿงต TL;DR

My lab just leveled up. Going from one node to a real multi-node Kubernetes setup opens the door to high availability, better simulation of production-grade environments, and hands-on experimentation with real-world scenarios โ€” all without breaking the bank.

Leave a Comment