You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2 x 3TB HDD (SMR for backups), 2 x 8TB HDD, 1 TB NVME, 256GB NVME for storage pool cache
NFS Server
DSM 7
Network
Vendor
Model
Function
Juniper
EX2200-48P-4g
Hallway switch with PoE+ and fiber uplinks to rack
Juniper
EX3300-48P
Rack switch with PoE++ and 10G SFP+
TP-Link
TL-SG108E
Bedroom switching behind desk
Mikrotik
RB5009
Main router
All nodes are connected to a dual-stack network, with private IPv4 and public IPv6.
Kubernetes' nodes are on their own VLAN which has access to the NAS.
☁️ Cloud Dependencies
While most of my infrastructure and workloads are self-hosted I do rely upon the cloud for certain key parts of my setup. This saves me from having to worry about two things. (1) Dealing with chicken/egg scenarios and (2) services I critically need whether my cluster is online or not.
The alternative solution to these two problems would be to host a Kubernetes cluster in the cloud and deploy applications like HCVault, Vaultwarden, ntfy, and Gatus. However, maintaining another cluster and monitoring another group of workloads is a lot more time and effort than I am willing to put in.