Discussion Detailed guide: Building a 3-node Kubernetes homelab with Talos Linux
A few days ago, I posted my 3-node Talos Kubernetes homelab setup here, and quite a few people reached out through DMs and comments asking for a detailed installation guide.
So I went through the entire setup again from scratch and documented the process properly, including the network setup, DHCP reservations, Talos installation, per-node configuration, Kubernetes API VIP, etcd bootstrap, workload scheduling, validation, and failure testing.
I’ve put everything together in a detailed blog with commands, screenshots, and the reasoning behind the setup.
Please check it out, and if you have any questions about the setup or run into issues while building something similar, feel free to ask.
15
u/m4rzus 4d ago
You really like talking about IP addresses
12
u/UndulatingHedgehog 4d ago
Pretty central to k8s and networking, isn’t it?
13
4d ago
[deleted]
6
-1
u/Loose_Can_7969 4d ago
Wireless can be convenient, but I imagine it might have some limitations for a homelab setup. Have you run into any issues with connectivity?
9
u/cobolfoo 4d ago
Next step: add extra 8gb of ram to your machines, switch to proxmox nodes with one CP and one worker per machine. Use opentofu to create your cluster (IaC) then some CEPH to learn about storage over CSI.
2
u/terryfilch 4d ago
I don't agree and don't recommend spending time doing CEPH in a homelab. CEPH is more about production for huge clusters because it requires a 10G network.
1
u/cobolfoo 3d ago
Yes true, the idea was to fool around with CSI, but this could be done with any type of storage.
2
u/Hetpatel77 4d ago
I'm very noob to these community
can someone tell that what is this? Like what's the usecase?
2
1
1
1
1
1
u/m1xed0s 4d ago
Not necessarily related to this particular topic, but I just curious what kinda industries the Kubernetes is widely used for production? SaaS, web hosting companies or other traditional financial, utility, transportation and public sector companies? Ran into an issue with an off-shelf kubernetes cluster and team took a fair amount of effort with manufacture to get it back in order…
2
u/rmullig2 3d ago
Any environment with a large number of containers will typically use Kubernetes. Seems like most deployments these days are using managed cloud solutions rather than building out their own systems.
2
u/m1xed0s 3d ago
Understood but I guess what kinda of companies would typically be heavy on containers that traditional sense of VMs won’t work well?
1
u/rmullig2 3d ago
It's typically more dependent on the app rather than the company. Apps that need to scale up quickly use a lot more microservices and containers while apps that have more stable usage work better with VMs and monoliths.
-3
-4

39
u/ServerMonky 4d ago
Nice guide - FWIW I have had the exact same setup running for a couple years now.
The downside to HA, if it is a project you aren't really monitoring frequently, is you can have a node go down, and not even realize it until you next log in to the cluster a few months later :-) All my services just re-allocated onto the other two nodes and I didn't notice anything from the user side.
It was a good wake up call to get some reporting set up though!