Multi-Node Local Kubernetes with vind: Pod Scheduling, Node Drains, and Affinity Rules

Yesterday we got started with a single-node vind cluster . That’s great for basic development, but if you want to test pod scheduling, node affinity, anti-affinity, topology constraints, or node drains, you need multiple nodes. With KinD, multi-node configs work but you’re still limited to local Docker containers with no external node support. vind gives you the same multi-node Docker setup, plus the option to add real cloud nodes later (we’ll cover that in Day 4). Today, let’s create a 4-node cluster and put it through its paces. The Configuration Create a multi-node.yaml file: experimental : docker : nodes : - name : worker-1 - name : worker-2 - name : worker-3 That’s it. This tells vind to create 3 additional worker nodes alongside the control plane. Each worker runs as its own Docker container with kubelet, kube-proxy, and Flannel. Create the Cluster Command: vcluster create multi-node -f multi-node.yaml Output: 12:57:42 info Using vCluster driver 'docker' to create your virtual cl