Auto-import images into the embedded registry about k3s HOT 4 OPEN

Thanks for the additional context. I'll leave this on the backlog.

from k3s.

The Spegel embedded registry mirror only supports mirroring things that can be loaded into containerd's image store. It has no store of its own. Containerd does not, as far as I know, support storing arbitrary OCI artifacts in its image store.

Feel free to open an issue at https://github.com/XenitAB/spegel and/or https://github.com/containerd/containerd - once they support it, we can too.

from k3s.

Or perhaps I'm misunderstanding what you mean by "miscellaneous" / "arbitrary" OCI images. Are you just asking for periodic re-import of tarballs from the images directory, instead of only importing them on startup?

That's been asked for in the past, but hasn't been prioritized. Homebrewing something with ctr -n k8s.io image import is probably your best bet.

from k3s.

As an example, I want to deploy bitnami/zookeeper to k3s in an airgapped environment.

• I can host the helm tgz in /var/lib/rancher/k3s/server/static/charts
• I can auto-deploy the helm chart using a manifest HelmChart CRD in /var/lib/rancher/k3s/server/manifests

But I can't load the zookeeper.tar containing the container image into the new embedded registry, without manually running k3s ctr images import zookeeper.tar. It'd be great if I could drop in that zookeeper.tar to a directory on the k3s server, and it auto-loads that image into the registry

from k3s.