-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
appendMirrors does not work as expected with RKE2 versions higher than v1.28 #648
Comments
RKE2 and K3s do not support standalone spegel deployments. Those distros manage their containerd config files, and will override the outside "interference" of spegel deployed as a helm chart. See https://docs.k3s.io/installation/registry-mirror (the same stuff applies to RKE2). |
tl;dr spegel is built into rke2 already. Uninstall the spegel chart, add Upgrade to a non-EOL release of RKE2 first though. Both 1.27 and 1.28 are end of life, and you're not even on the most recent patch release. |
Thank you for the suggestions. Can you help me how can I read the spegel logs when using |
Per the docs (with equivalent rke2 versions)
|
Upgrade!!! |
Spegel version
v0.0.27
Kubernetes distribution
RKE2
Kubernetes version
v1.29.3
CNI
Calico
Describe the bug
First of all thanks for this awesome project, it helps a lot!
I have 2 RKE2 clusters with version 1.28.7 and one with 1.27.10 that pull images from a private gitlab registry with the content of /etc/rancher/rke2/registries.yaml:
If i set
appendMirrors: true
in the helm chart values, it merges the hosts.toml file as expected:Now with other RKE2 clusters of versions 1.29.3, 1.30.1 and 1.30.5 it does not merge the files. The content of /etc/rancher/rke2/registries.yaml is exactly the same in all clusters but I end up with the config file like this:
while the hosts.toml file from _backup folder looks like this:
and I end up getting
x509: certificate signed by unknown authority
error when pulling new images from this private registry, while already existing images are pulled from other nodes as expected.In the configuration container log it says that it appended the configuration:
here is my values file for all clusters:
The text was updated successfully, but these errors were encountered: