Day 1: Introduction to vind: Why I Replaced KinD with vCluster in Docker [vind]

If you’ve been working with Kubernetes for a while, you’ve probably used KinD (Kubernetes in Docker). I’ve used it extensively for my local development, CI pipelines, demos, you name it. And for what it does, it works. But I’ve always felt like there was something missing. That’s why we built vind to solve some of the shortcomings of KinD. What is vind? vind stands for vCluster in Docker. It’s a new way to run local Kubernetes clusters using the Docker driver. Instead of spinning up KinD clusters, you use the same vCluster CLI you might already know but pointed at Docker as the backend. The result? A local Kubernetes cluster that runs entirely in Docker containers, just like KinD, but with a bunch of features that KinD simply does not have. Why I Switched Overall KinD is great for basic use cases. But the moment you need anything beyond a simple single-node cluster, you start hitting walls: No LoadBalancer support: You need MetalLB or some workaround. With vind, LoadBalancer services w