I'm learning Kubernetes and wondering what I'd gain from setting up a cluster with kubeadm instead of using a managed service. Can I try it on one machine?
Is building a kubeadm cluster worth it when managed Kubernetes exists?
Answers
Yes, doing it once can make the managed services a lot less mysterious. You'll see how the container runtime and kubelet fit in, how the control plane starts, and how worker nodes join.
You'll also have to deal with cluster networking, certificates and kubeconfig. That gives you a better picture of what's behind the scenes when something breaks, even if you go back to a managed cluster afterward.
Reply to this answer
One physical machine is enough if it can run a few virtual machines. Try one VM for the control plane and two for workers. That gives you separate nodes to join and lets you explore the setup without finding extra hardware.
Reply to this answer
For a structured route, look for a kubeadm cluster setup guide. Kubernetes the Hard Way is another learning exercise if you want to dig further into the moving parts rather than relying on kubeadm to bootstrap them.
Reply to this answer
It depends what you want to learn. A lightweight distribution such as k3s can get you a cluster, but kubeadm gives you a chance to work through more of the standard setup. That extra work is the point if cluster administration is your goal.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_t84+bytecaddy.3:
You can also start smaller if your machine is short on resources, then add workers when you're ready to explore node joining.