This message was deleted.

I don't think

kind

will work; I would suggest

k3d

if you really need multi-node clusters.

we were trying to use

act

to test a thing where we'll eventually be using

helm/kind-action

.

Thanks, that is good to know. And would be great to collect in an issue.

I'll try to do that soon, but not now

I'm not sure if

kind

is fixable as long as Rancher Desktop uses Alpine as the VM image. OTOH

k3d

is working, so not sure what it is that is breaking

kind

. Initially it was cgroup v2 support, but even with that fixed,

kind

still failed for me. And then I ran out of time investigating it.

I can definitely give steps to reproduce because it's trivial

Steps to reproduce what?

It should be

brew install act

, create a repository with this workflow https://github.com/helm/kind-action#example-workflow, and then use

act

I've asked Matt why there is no

helm/k3d-action

, and he basically said "because you didn't write it"... 🙂

Heh

Anyways,

kind

already fails from the shell like this:

$ kind create cluster -v 9
Creating cluster "kind" ...
DEBUG: docker/images.go:67] Pulling image: kindest/node:v1.27.3@sha256:3966ac761ae0136263ffdb6cfd4db23ef8a83cba8a463690e98317add2c9ba72 ...
 ✓ Ensuring node image (kindest/node:v1.27.3) 🖼
 ✓ Preparing nodes 📦
 ✗ Writing configuration 📜
Deleted nodes: ["kind-control-plane"]
ERROR: failed to create cluster: failed to generate kubeadm config content: failed to get kubernetes version from node: failed to get file: command "docker exec --privileged kind-control-plane cat /kind/version" failed with error: exit status 137

Yeah, that looks like what we saw

As I wrote above, having Github issues, especially with upvotes from additional users, makes it more likely that someone will look into it

As others can attest, I'm not shy about filing. I'm just out of the office atm.

Matt Farina, one of the

helm

maintainers (they are all called Matt by some accident)

Lol

The others are Matt Butcher and Matthew Fischer, aka the 3 Matts...

Ok, this is not what I thought it was... OotB, I think RD has 2 cpus assigned. Sometimes I get this:

kind v0.17.0

vs

kind v0.20.0

I have runs where v0.20.0 is ok

I think recent releases of

kind

just require

systemd

...

macOS

Please file an issue and add all the details; I don't have time to look into it now

ok. I feel lousy about filing a thing that I can't reliably reproduce 😞