Setting up a multi-arch Kubernetes cluster at home

submited by

Style Pass

2021-06-19 17:00:04

I still remember my Lobste.rs comment, mocking some guy for running Kubernetes for his static blog — it is my highest voted comment after all. But to be fair, I’m not running mine for a static blog. In fact, I’m not even hosting my blog on the cluster; but I digress. Why did I do this anyway? Simply put: I was bored. I had a 4 day weekend at work and with nothing better to do to other than play Valorant, and risk losing my hard earned Bronze 2 — I decided to setup a K8s cluster. These are the nodes in use:

The Oracle machines are the free tier ones. It’s great — two static public IPs, 50 gigs of boot volume storage on each + up to 100 gigs of block volume storage. All for free.1 Great for messing around.

I considered running K3s, because it’s supposedly “lightweight”. Except it’s not really vanilla Kubernetes — it’s more of a distribution. It ships with a bunch of things that I don’t really want to use, like Traefik as the default ingress controller, etc. I know components can be disabled, but I couldn’t be arsed. So, kubeadm it is.

Since I’m going to be using Flannel as the CNI provider, I set the pod network CIDR to Flannel’s default. We also want the Kube API server to listen on the Wireguard interface IP, so specify that as well.