With version 2.0, my homelab actually will have a load balancer in front of the K8s cluster. In a public cloud environment, the cloud provider would be the ones to provide this. In my case, since load balancing is a pretty light task, I’m using my lower power surface to do the job. I chose HAproxy because I liked it’s simple config file syntax.
Since there was a lot of headroom to run other stuff on my surface in addition to HAproxy, I decided to setup DNS over TLS for my Pi-hole. Read More...
I got my hands on a old Raspberry Pi and decided that will have the sole purpose of running Pi-hole since I didn’t know what else to use it for.
As for Kubernetes, I wanted a cluster, which is why I had a 2 computers runing MicroK8s that served as two K8s nodes. However, I realized that my ISP’s gateway didn’t jive with MetalLB.
I wanted to set a different IP for each of my services so I can map custom DNS to each website that I serve. Read More...
I must have lost all self-respect. I can’t believe I’m turning my website into a blog. Anyways, this site is only meant as a place for me to document the evolution of my homelab.
You probably already saw the diagram I made on the homepage, which I will be updating as time goes on. I’ll post previous versions of the diagram in later posts too.
I started a homelab because I traded my old graphics card for a broken PC. Read More...