Issue with Embedded Registry Mirror Usage

[ysicing]

Environmental Info:
K3s Version: v1.28.10+k3s1

Cluster Configuration: 3 servers

I deployed a 3-node k3s cluster with 3 masters. After deployment, I enabled the --embedded-registry feature on all 3 machines, but only one machine seems to be listening on port 5001.

Additionally, when I run kubectl get --raw /api/v1/nodes/k8s02/proxy/metrics | grep -F 'spegel', I can only see data from the node listening on port 5001.
Is this behavior expected? If not, how should I fix this issue?

[brandond]

Did you follow the instructions in the documentation to configure registries.yaml on all your nodes? registries.yaml is configured individually on each node; if no registries are enabled for mirroring the embedded registry mirror will not start on that node.

[ysicing]

@brandond Of course, I've configured each node /etc/rancher/k3s/registries.yaml

[brandond]

Please attach the k3s logs from journald on the nodes where you don't see the embedded registry starting.

[ysicing]

@brandond thank you. My problem, /etc/systemd/system/k3s.service format problem, lead to ignore the configuration.