Megarepo for my personal homelab
I'll make a pretty diagram and or include some photos at some point
- 1x Square D Home Electronics Protective Device 80 kA
- 2x Leviton 20 Amp Hospital Grade Surge Outlet
- Each outlet has a dedicated 20A breaker, this was done for a future deployment of multiple UPS each would get their own outlet / breaker
- 1x APC AP7801 Metered Rack PDU
- Version 1 of the power managment in the rack, UPS coming soon
- 1x StarTech.com 1U 19in Metal Rackmount Cable Management Panel
- This is used to tidy up the power cables coming to the bottom of the rack into the APC AP7801 PDU
- 1x Ubiquiti Dream Machine Special Edition
- 1x Ubiquiti Switch 24 POE
- 2x Ubiquiti U6 Lite Access Point
- 1x Ubiquiti AC Mesh Pro Access Point
- 1x TRENDnet 24-Port Keystone Shielded 1U Patch Panel
1x TRENDnet 10-Port Gigabit POE+ SwitchReplaced by Ubiquiti Switch 24
- 1x Dell PowerEdge R240
- 1x PERC H330
- 4x 8TB WD Red Plus NAS 3.5" Drive (32TB Total)
- 1x PERC H330
- 1x Dell PowerEdge R620
- 2x Intel(R) Xeon(R) CPU E5-2620 @ 2.00GHz
- 6x 16GB DIMM DDR3 Synchronous Registered (Buffered) 1333 MHz (96GB Total)
- 1x NVIDIA Quadro M20004GB GDDR5 GPU
- 1x GLOTRENDS M.2 PCIe NVMe Adapter
- 1x 250GB Samsung 970 EVO Plus NVMe M.2 Internal SSD (Boot Drive)
- 1x PERC H710 (Flashed IT Mode)
- 1x 1GB Crucial MX500 2.5" SSD (Longhorn Disk)
- 1x Dell PowerEdge R430
- 2x Intel(R) Xeon(R) CPU E5-2660 v4 @ 2.00GHz
- 2x 8GB DIMM DDR4 Synchronous Registered (Buffered) 2133 MHz (16GB Total)
- 1x GLOTRENDS M.2 PCIe NVMe Adapter
- 1x 250GB Samsung 970 EVO Plus NVMe M.2 Internal SSD (Boot Drive)
- 1x PERC H730 Mini (Flashed IT Mode)
- 1x 1TB Crucial MX500 2.5" SSD (Longhorn Disk)
- 1x Dell PowerEdge R330
- 1x GLOTRENDS M.2 PCIe NVMe Adapter
- 1x 250GB Samsung 970 EVO Plus NVMe M.2 Internal SSD (Boot Drive)
- 1x PERC H330 (Flashed IT Mode)
- 1x 1TB Crucial MX500 2.5" SSD (Longhorn Disk)
- 6x 2TB Crucial MX500 2.5" SSD (12TB Total)
- 1x GLOTRENDS M.2 PCIe NVMe Adapter
I'm using k3s as my Kubernetes flavour. It was super easy to get up and running and is much less resource heavy then other options. I had previously tried to use microk8s and ended up with a unrecoverable cluster failure.
curl -sfL https://get.k3s.io | sh -s - server \
--cluster-init \
--cluster-cidr 10.34.0.0/16 \
--service-cidr 10.35.0.0/16 \
--cluster-dns 10.35.5.5 \
--write-kubeconfig-mode 644 \
--bind-address 0.0.0.0 \
--advertise-address 10.33.0.1 \
--disable traefik \
--disable servicelb \
--disable local-storage \
--flannel-backend=host-gw
| CIDR | Description |
|---|---|
10.33.0.0/12 |
UniFi VLAN |
10.34.0.0/16 |
K3s Pods |
10.35.0.0/16 |
K3s Services |
10.36.0.0/16 |
MetalLB External Addresses |
just deploy system/metal-lb
just deploy system/twingate
just deploy system/traefik
just deploy system/cert-manager
just deploy system/longhorn
Here is a list of self-hosted applications I might add in the future: