4 ms·
I tried pretty much all of them and settled with kind. It takes 1 command and 1 minute to spin up a 3 node cluster from scratch, everything works the same as y
by nickjj 5y ago
I tried pretty much all of them and settled with kind.
It takes 1 command and 1 minute to spin up a 3 node cluster from scratch, everything works the same as you would expect on a real managed Kubernetes cluster and it took a few lines of YAML to config the cluster so that the ingress works in such a way where you can write your manifests exactly how you would on a managed provider. It's also super easy to get your local Docker images into the cluster.
Did anyone else come to the same conclusion? Maybe I'm missing something but you can't really ask for much more than the above.
- 8bitbuddhist 5y agoAgreed, Kind is perfect for running disposable, reproducible multi-node clusters that are essentially upstream K8s.
- stonecharioteer 5y agoFirst time I've heard of Kind. I run k3s and minikube. How is Kind different?
- nickjj 5y agoI had lots of trouble with minikube. Often times it failed to create a cluster with low level networking issues related to hyper-v. It was really flaky. I could delete and create a cluster and it felt like half the time it worked, half the time it failed. I was using the Docker back-end too. For k3s, it mainly comes down to wanting to use k8s not k3s. I'd like my local cluster to be as close as possible to what's running in a real managed k8s cluster on a major cloud provider. This might come off as naive but I want to use k8s in dev / local testing because I'm using k8s in production. I also found kind's documentation much better than k3s for wanting to accomplish the task of setting up a cluster and using an ingress. It also had easy to find and follow docs for WSL 2 to configure extra port mappings in the cluster config so I could access external services (managed with an nginx ingress) over a defined port. Basically the dev experience has been flawless.