Running kubernetes in your homelab is complex, time consuming, there are almost no docs to help you (homelab focused docs for things you want to install), and nothing is copy paste. You have to make everything happen yourself.
The Wrong Reasons To Run Kubernetes In Your Homelab #
- I run compose and think kubernetes is the next logical step
- Techno Tim runs it
- I heard itβs what cool kids do
- Kubernetes BTW
- Talos Linux looks cool
- I found a cool helm chart on GitHub
- I need scale
There are also The Right Reasons To Run Kubernetes In Your Homelab.
I run compose and think kubernetes is the next logical step #
No itβs not. Itβs much different than running docker, compose, swarm. Itβs meant for scale, itβs complex, itβs made for enterprise, not your local development or your homelab. It can do these things, it can do them quite well, but itβs not the target audience.
Techno Tim runs it #
I heard itβs what cool kids do
You need to rethink who the cool kids are, touch some grass. Tim also does it for his job, he likes it, he knows it, he wants to lean on it and learn more.
Kubernetes BTW #
Kubernetes does not make you look cool, it makes you look like you are trying to over optimize and over engineer your life. Itβs not worth it, in fact nothing in life is worth worrying about what everyone else thinks of you.
Talos Linux looks cool #
Talos is an S tier OS wherever you deploy it. It is a secure, minimal, kubernetes first OS. They also have some really great people working there putting Talos in some really cool places like backpack or Apple Power Mac
I found a cool helm chart on GitHub #
No you didnβt. Everything in homelab is compose first. A few things have a k8s option, but almost nothing is k8s first.
I need scale #
No. Youβre homelab does not need scale. If you think it does, you have some real shit hardware, some bad optimizations, or somehow you have a startup you need to launch cause you got more users than most.