Can't pull images from local registry

We're missing configuration from the /etc/containerd/config.toml to allow kind to pull images from the local registry spun up by --registry.

I'll open a PR to add the configuration as part of the containerdConfigPatches in kind.go.

The required configuration is:

    [plugins."io.containerd.grpc.v1.cri".registry.mirrors]
      [plugins."io.containerd.grpc.v1.cri".registry.mirrors."kind-registry:5000"]
        endpoint = ["http://kind-registry:5000"]
    [plugins."io.containerd.grpc.v1.cri".registry.configs]
      [plugins."io.containerd.grpc.v1.cri".registry.configs."kind-registry:5000".tls]
        insecure_skip_verify = true

This configuration is required, e.g., for Apache Camel-K to be used with kn quickstart. Without this configuration, no images can be pulled from the local registry.

[psschwei]

Thanks for opening the issue. Do you know if this is something impacting all local registry use, or is it something specific when using Camel-K?

As I understand it, this should impact all local registry use*. The issue is the kind can't pull from the local registry without either A) certificate configuration, or B) telling it that the local registry uses HTTP and that we should skip TLS verification.

*where the user is using the registry set up via the --registry flag.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[Evynglais]

Apologies for the delay and the confusion (closing and reopening the PR). I had a secondary account and have reopened the PR under my primary account and deleted the secondary.

The CLA requirement is now complete (which is what I believe you were waiting for me to do).

[Evynglais]

/reopen

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.