ctlptl v0.8.25 has broken cluster config with containerdConfigPatches about ctlptl HOT 3 CLOSED

hmmmm...i'm not sure how to resolve this.

The problem is that kind v0.20.0 has deprecated containerd CRI mirrors, see https://github.com/kubernetes-sigs/kind/releases/tag/v0.20.0. It currently has a compatibility shim but it doesn't work in all cases. And the plan is that this will break upstream soon.

i filed a feature request here for a better api for this - kubernetes-sigs/kind#3354 - but the root of the issue isn't even Kind, it's upstream containerd deprecations.

from ctlptl.

Thanks for this @nicks - this is incredibly useful information, as I wasn't aware of the changes.

I've attempted to make the necessary changes, but it seems that insecure registries aren't supported (or I've made some misconfiguration): containerd/containerd#9454

from ctlptl.

I resolved this by upgrading to v0.8.28 and making the following amendments:

In the cluster-config.yaml:

apiVersion: ctlptl.dev/v1alpha1
kind: Cluster
product: kind
name: kind-mycluster
kindV1Alpha4Cluster:
  containerdConfigPatches:
    - |-
      [plugins."io.containerd.grpc.v1.cri".registry]
        config_path = "./containerd"

And introducing a file at the following path, containerd/example.internal:5001/hosts.toml:

server = "http://example.internal:5001"

[host."http://example.internal:5001"]
 capabilities = ["pull", "resolve", "push"]
 skip_verify = true

from ctlptl.