Build a Kubernetes cluster from bare Raspberry Pis. Then pull the plug on one.
HomeK8s kits arrive with the OS, containerd and kubeadm installed, and nothing else. You prepare the nodes, run kubeadm init, install the network and break things on purpose, guided step by step from your browser. No screen or keyboard needed.
From $228 · ships from Australia · leave any time and keep the cluster
$ sudo kubeadm init --pod-network-cidr=10.244.0.0/16Run[init] Using Kubernetes version: v1.37.1
[preflight] Running pre-flight checks
[certs] Generating "ca" certificate and key
[control-plane] Creating static Pod manifest for "kube-apiserver"
[etcd] Creating static Pod manifest for local etcd
Your Kubernetes control-plane has initialized successfully!The kits
One Pi. Build a real cluster from a bare node.
- Node prep: swap, kernel modules, sysctls
- kubeadm init and a pod network
- Deployments, services, self-healing
Three control-plane nodes. Pull a plug, watch it survive.
- Everything in Solo
- Highly available control plane with stacked etcd
- Quorum: what fails when two of three go down
Three control-plane nodes, two workers. Closest to production.
- Everything in Trio
- Draining, cordoning and rolling upgrades
- Pod spreading, disruption budgets, chaos drills
How it works
Power and an ethernet cable. The Pi comes up in tutorial mode and checks in with the portal.
Enter the code from the card in the box and read exactly what the Pi will share. Nothing happens until you agree.
A real terminal on your Pi in a browser tab, from anywhere. Each step checks your work on the Pi itself.
Offboard in one click: the agent removes itself and the cluster is entirely yours, even for production.
The Pi keeps one connection out to HomeK8s, and your terminal travels through it. Nothing ever connects in, and your router needs no changes.
- Terminals open only for you, or an admin you approve, for a time you choose
- Your kubeconfig, certificates and join tokens never leave the Pi
- One small program. No extra packages, and gone completely when you offboard
6 lessons, from a bare node to rollouts
- 015 minMeet your PiOpen a terminal on your Pi from anywhere, and run your first commands.
- 0215 minPrepare the nodeSwap, kernel modules, sysctls and the container runtime: what kubelet needs before a cluster can exist.
- 0320 minCreate the control planekubeadm init: certificates, etcd, the API server, and your kubeconfig.
- 0410 minInstall a pod networkGive pods addresses and routes with Flannel, then let workloads run.
- 0515 minYour first deploymentRun nginx, expose it with a Service, and write a manifest in the editor.
- 0615 minSelf-healing and rolloutsDelete pods, watch them come back, scale up and roll out a new image.
Trio and Quint add a highly available control plane, quorum drills, draining and upgrades.
Questions
k3s hides the parts you're here to learn. kubeadm is what the CKA exam and most self-managed clusters use: certificates, static pods, etcd, CNI, all visible.
Keep going for a small monthly subscription, or offboard for free. Either way the hardware and the cluster are yours.
Yes. Offboarding removes HomeK8s completely. What's left is a standard kubeadm cluster on Raspberry Pi OS.
No. Plug in power and ethernet (Wi-Fi works too). Everything else happens in your browser, and SSH is there if you want it.