what is the different between running kubeadm in Vagrant vs running kubeadm in Docker vs KinD?

I am new to k8s and based on my research kubeadm and its modularity make a lot of sense for my work. Based on what I have seen so far to create a multi node cluster Vagrant is usually chosen. I have seen some older projects with kubeadm in Docker but they seem to be not maintained and they point to KinD. Based on what I know so far KinD is more limited compared to Kubeadm. I wonder what are the limitations of running kubeadm and different nodes in different docker containers?

1 thought on “what is the different between running kubeadm in Vagrant vs running kubeadm in Docker vs KinD?”

  1. can you elaborate on the “more limited compared to kubeadm” bit? I believe kind uses kubeadm on the nodes running in containers. for testing I’ve been able to do everything I needed using kind. if I needed vms for some reason I might consider minikube.

    Reply

Leave a Comment