This message was deleted Rancher Users #k3s

Join Slack

This message was deleted.

# k3s

adamant-kite-43734

10/13/2023, 8:08 AM

This message was deleted.

✅ 1

creamy-pencil-82913

10/13/2023, 8:23 AM

1. You don’t need to add a mirror for your registry if the endpoint is the same as the hostname.

<https://harbor.k8s.lan>

is the default endpoint for a registry named

harbor.k8s.lan

. 2. Unfortunately since you did add an endpoint, it is using that. However, your endpoint includes a port, but your config key does not.

harbor.k8s.lan:443

is not the same as

harbor.k8s.lan

- yes that’s the default port for https, but the code is matching strings here.

creamy-pencil-82913

10/13/2023, 8:23 AM

tl;dr all you need is

Copy code

configs:
  "harbor.k8s.lan":
    tls:
      insecure_skip_verify: true

creamy-pencil-82913

10/13/2023, 8:23 AM

drop everything else

creamy-pencil-82913

10/13/2023, 8:25 AM

Note how all the examples in the docs have the same host:port value in the endpoints and configs. Either include the port, or don’t - but be consistent. https://docs.k3s.io/installation/private-registry

prehistoric-judge-25958

10/13/2023, 8:26 AM

Thanks I will try that tonight 🙂 The funny thing is that this has worked before, so I am a bit confused. All I did was init a new Harbor instance.

prehistoric-judge-25958

10/13/2023, 8:49 AM

btw, will a change in

/etc/rancher/k3s/registries.yaml

be applied after

systemctl restart k3s

creamy-pencil-82913

10/13/2023, 9:06 AM

yep

👍 1

prehistoric-judge-25958

10/13/2023, 12:49 PM

Thanks. It is working now!

Open in Slack

Previous Next