Hello,
Is there a way to configure an insecure container registry when provisioning a new K3s cluster via Rancher?
Currently, we’re manually creating the following file on the provisioned node:
/etc/rancher/k3s/registries.yaml
This works initially, but after a reboot, the file is reset. We suspect Rancher is overwriting it during reconfiguration.
What’s the correct or recommended way to persist registries.yaml (with an insecure registry) in a Rancher-managed cluster? Ideally, we’d like to set this during provisioning to avoid manual patching per node.
Thanks in advance!
Sam