Create a new single node cluster with embedded registry mirror does not work about k3s

[brandond]

If you're using it standalone then the upstream docs are relevant. If you're using the embedded Spegel, I would stick to the k3s docs as it is literally embedded in and its configuration managed by k3s.

[vitobotta]

Yeah I also thought there would be a daemonset because of the way standard Spegel works. So I am not sure why is it surprising that we had that kind of expectation somehow. I also got it working nicely in the meantime.

[vitobotta]

I can't get the embedded registry to work either. I am using the flag for the servers, have opened port 5001 and created the registries.yaml so that all registries are mirrored, but nothing happens. There is no sign of Spegel anywhere in the cluster and the images are not being distributed between nodes. I know that for sure because the reason why I want to use it is as a workaround for a know issue with some Hetzner IPs being banned from some registries. When I install Spegel via Helm, a daemonset is created and nodes exchange images as expected (confirmed both by the logs and by the pods starting on all nodes without any issues). But with the embedded registry mirror enabled with the flag I don't see any of this.

[brandond]

No spegel daemonset is created. I expected a daemonset to be created when adding --embedded-registry

Spegel is embedded in the main k3s process. What did you see that made you expect to see this deployed as a daemonset?

I will also note that you didn't mention configuring any registries in registries.yaml. Please reference the documentation again for required configuration.

[frederikhs]

No spegel daemonset is created. I expected a daemonset to be created when adding --embedded-registry

Spegel is embedded in the main k3s process. What did you see that made you expect to see this deployed as a daemonset?

I will also note that you didn't mention configuring any registries in registries.yaml. Please reference the documentation again for required configuration.

In the Architecture section of the Spegel readme, it is stated that

Spegel is deployed as a Daemonset on each node which acts as both the registry and mirror

And thus my understanding was that this was what was going to happen in k3s with the --embedded-registry flag.

I have added registries.yaml to the all nodes in a larger cluster and tried pull an image on one node, then deleting the image tag in the registry and scaling the deployment to see if the image is getting pulled using the embedded registry, and it worked! Is there a place i can look for logs so debugging later on?