I 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

I 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.