Benjamin Ullian

As a temporary workaround, the crd will deploy (on 1.18 in my case) by removing the instances of `protocol` from the several `x-kubernetes-list-map-keys` arrays in the generated crd.

fwiw, i also tried this in a HostProcess pod and got the exact same result, which is somewhat surprising since that should be equivalent to running buildkitd.exe directly on the...

It didn't, same error. After filing this issue I tried the HostProcess pod, same issue, and then tried buildctl+buildkitd **directly** on the kubelet host which _also_ failed with the same...

And yes I was ideally trying to build a container from inside another - but HostProcess would be okay if I could get it to work too, my goal is...

Gonna give this a shot and report back!

I did! I was able to have `buildctl` in a container which mounts the buildkitd named pipe from the host (buildkitd has to run on the actual physical host, not...

We have encountered this issue on all of our ~12 clusters. It is definitely an EKS issue and not a terraform issue since deleting and recreating the fargate profile (either...

I was able to reproduce this easily in `kind` by making 3000 ingresses pointing to 3000 services, and looping over one of the ingress hosts using curl while doing a...

It was kind 3-worker cluster on a host with 8 core / 16 threads and 64g memory, not a laptop but nothing crazy. I am not sure I really need...