Cannot use registry mirror

[AliRezaBeitari]

I'm using k3s and I have a Private Registry Configuration in which I've added a mirror:

/etc/rancher/k3s/registries.yaml:

mirrors:
  helloworld.k8s:
    endpoint:
      - "https://***************"
configs:
  "***************":
    auth:
      username: ****
      password: ****

Then, I deployed Keel using Helm, but I can see these errors in the logs:

time="2023-12-09T16:57:47Z" level=error msg="trigger.poll.manager: got error(-s) while watching images" error="encountered errors while adding images: Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/this-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host, Head \"https://helloworld.k8s/v2/his-is-test/my-image123/manifests/latest\": dial tcp: lookup helloworld.k8s on 10.43.0.10:53: no such host"

It seems Keel does not know helloworld.k8s is just a mirror to the actual registry endpoint.

Is there any way to tell Keel to read the /etc/rancher/k3s/registries.yaml file and act accordingly?

[bowen-facere]

Hey I'm running into the same situation as you, did you ever find a resolution to this?

[AliRezaBeitari]

Hey I'm running into the same situation as you, did you ever find a resolution to this?

Hey,
Unfortunately no! I ended up using the real registry hostname and for the username/password, I used imagePullSecrets for every single Deployment I have. I know it's messy, but at least it works.