https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
c
if you’re using rancher to provision the cluster, you need to use rancher to configure the cluster. the registries file is being managed by rancher and will get reset back to whatever you configured in rancher.
l
I just figured it out, I was restarting 2 services (wasn’t sure how RKE2 was supposed to be restart as the docs said to do so found those 2 and restarted them…) Turns out I just needed to restart 
rke2-server.service
, after doing that the private container registry with no HTTPS is working!
Is there a way I can setup registries.yaml instead of doing it manually on each node?
The doc says -
Copy code
If you wish to use a private registry, then you will need to create this file as root on each node that will be using the registry.
c
do it via rancher, as I mentioned earlier
l
Is there documentation to do that? I’m new to all things Rancher/k8s
Not sure where I’d set that in the Rancher server UI, using 2.8
c
you’re looking at resources in the cluster, you need to look at the cluster itself.
Go into Cluster Management in the top left menu, then click into the cluster in question, then go to Config at the top right.
then go into the Registries section, and click “Enable cluster scoped registry”. You can leave the two sections at the top blank, but then add your registry name and endpoint to the mirrors section.
when you save that, it’ll apply it to registries.yaml on the nodes, and restart the service.
l
Awesome found it, TY!
Open in Slack
PreviousNext
Powered by