It takes longer to set up a Kind cluster with this action than Minikube

I'm switching to Kind to get better performance but I'm actually getting a performance regression after switching from Minikube: https://github.com/relaycorp/relaynet-internet-gateway/pull/269/commits/16a32302667e26b58201c8a66bec019bac968cdd

With that Minikube action, I'd have a cluster set up in 1m35s give or take. With this action, it takes more than 2 minutes.

I'd expect this action to be as fast (if not faster) than the original one for Minikube. Maybe I'm missing something?

Here's the output from this action in case it's relevant:

Installing kind...
Adding kind directory to PATH...
Installing kubectl...
Adding kubectl directory to PATH...
kind v0.9.0 go1.15.2 linux/amd64
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-09T11:26:42Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Creating kind cluster...
Creating cluster "default" ...
 • Ensuring node image (kindest/node:v1.19.1) 🖼  ...
 ✓ Ensuring node image (kindest/node:v1.19.1) 🖼
 • Preparing nodes 📦   ...
 ✓ Preparing nodes 📦 
 • Writing configuration 📜  ...
 ✓ Writing configuration 📜
 • Starting control-plane 🕹️  ...
 ✓ Starting control-plane 🕹️
 • Installing CNI 🔌  ...
 ✓ Installing CNI 🔌
 • Installing StorageClass 💾  ...
 ✓ Installing StorageClass 💾
 • Waiting ≤ 1m0s for control-plane = Ready ⏳  ...
 ✓ Waiting ≤ 1m0s for control-plane = Ready ⏳
 • Ready after 54s 💚
Set kubectl context to "kind-default"
You can now use your cluster with:

kubectl cluster-info --context kind-default

Have a question, bug, or feature request? Let us know! https://kind.sigs.k8s.io/#community 🙂

Note the Ready after 54s. Though I'm not sure how reliable that is.

helm / kind-action

It takes longer to set up a Kind cluster with this action than Minikube #28