利用Kubernetes kubeadm与minikube在虚拟机中创建多节点集群的疑问

Hey there! Let’s tackle your questions directly—both tools can help you build that 4-node cluster, but they’re built for different use cases.

Can Kubeadm create a 4-node cluster across separate VMs? #

Absolutely—this is exactly what kubeadm was designed for. It’s the official tool to bootstrap production-grade Kubernetes clusters, and scaling to multiple nodes (across VMs or bare metal) is straightforward. Here’s a quick overview of the workflow:

• Prepare your 4 VMs: Each needs to meet Kubernetes’ minimum requirements: a compatible OS (Ubuntu, RHEL, etc.), kernel version ≥ 5.4, a container runtime (Docker, containerd, CRI-O), and full network connectivity between all VMs.
• Initialize the control plane: Pick one VM to be your control-plane node. Run kubeadm init on it—this sets up the API server, etcd, and other core control-plane components. After initialization, follow the post-setup steps to configure your kubectl context.
• Join worker nodes: On each of the remaining 3 VMs, run the kubeadm join command provided by the kubeadm init output. This connects the worker nodes to the control plane seamlessly.
• Install a network plugin: Kubernetes requires a pod network add-on (like Calico, Flannel, or Weave Net) to enable communication between pods across nodes. Install one right after initializing the control plane (most have simple kubectl apply commands for their manifests).

Pro tip: Make sure your VMs have the necessary ports open (e.g., 6443 for the API server, 2379-2380 for etcd, 10250 for kubelet) and that DNS resolution works reliably between all nodes.

Can Minikube be used for multi-node clusters? #

Yes! While Minikube is most commonly associated with single-node development clusters, it absolutely supports multi-node setups. You can spin up a 4-node cluster (1 control plane + 3 workers) with a single command:

minikube start --nodes 4 --driver=virtualbox

(Note: The --driver flag depends on your hypervisor—use virtualbox, kvm2, hyperv, etc., based on what’s installed on your physical machine.)

Minikube handles all the heavy lifting: it creates the VMs, installs Kubernetes components on each, and configures the cluster automatically. It’s perfect for quick testing or development where you don’t need to customize individual node configurations.

That said, keep in mind Minikube is optimized for local development, not production. If you need fine-grained control over each node’s resources, OS settings, or network topology, kubeadm is the better choice.

Final Recommendation #

• Use kubeadm if you want to simulate a production-like cluster, customize each VM’s setup, or learn the full cluster bootstrapping process.
• Use minikube if you want a fast, low-fuss multi-node cluster for testing or development without manual VM configuration.

内容的提问来源于stack exchange，提问作者Mr.DevEng