Our experience with local k8s dev is the issues are more on the k8s distro side. So at least for local dev, I'm guessing the happier path is sticking with KinD approaches wrt WSL2. Our wsl2 docker testing was successful, even w GPUs, and bc of the file system seperation, felt more like native Ubuntu docker's imperceptible overheads vs the painfully slow OS X docker overheads (ex: npm run watch taking minutes vs seconds)