Rancher Turtles 相关的镜像拉取问题该怎么解决呢？看文档说rancher 2.13版本开始默认嵌入了，可是用了 如何使用国内资源安装 K3s - #4，来自 2sadeggs 论坛上的方法修改镜像源，但是 Rancher Turtles 相关的镜像源没法修改。要怎么处理呢？？
我尝试通过将rancher-turtles charts的yaml文件下载到本地进行之后，通过 helm upgrade rancher-turtles ./ -n cattle-turtles-system --force --debug也没有办法解决，因为 rancher-turtles 是 rancher 内部控制的，原理同为 K3s 和 RKE2 配置 Mirror 不能直接更改 containerd 的配置文件，而是修改相关 K3s 或 RKE2 的配置文件，让其自动生成。
尝试过删除rancher-turtles也无果，因为有定时任务会自动重建。因此到这里来咨询了。烦大佬帮忙处理一下！！！
大佬，你发的这个帖子中并没有说明 如何修改 rancher 附加组件的国内镜像，我是先按照你的博客 https://kingsd.top/2025/08/11/simple-ha/ 创建的3节点k3s高可用集群，然后结合rancher官方说明 Helm CLI 快速入门 | Rancher 和 如何使用国内资源安装 K3s 这个帖子的安装步骤 进行安装的，部署之后最终的情况如下
# 创建rancher集群的命令
helm install rancher rancher-latest/rancher \
--namespace cattle-system \
--set hostname=rancher.ssip.io \
--set service.type=NodePort \
--set bootstrapPassword=886c7f5ca597c48b971b129060637e6c \
--set rancherImage=registry.cn-hangzhou.aliyuncs.com/rancher/rancher \
--set systemDefaultRegistry=registry.cn-hangzhou.aliyuncs.com
#####
jtxiao@server-01:~$ kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
cattle-fleet-local-system fleet-agent-7669bbbb55-6m8nw 1/1 Running 0 17h
cattle-fleet-system fleet-controller-6b877f69bd-k2xv8 3/3 Running 0 17h
cattle-fleet-system gitjob-5978d99ff9-p4hkm 1/1 Running 0 17h
cattle-fleet-system helmops-7c88655c4d-bjvwp 1/1 Running 0 17h
cattle-system helm-operation-zpnbf 1/2 Error 0 39m
cattle-system rancher-68fb6dfd9d-7s5gw 1/1 Running 0 18h
cattle-system rancher-68fb6dfd9d-gqc6h 1/1 Running 0 18h
cattle-system rancher-68fb6dfd9d-kk4cx 1/1 Running 0 18h
cattle-system rancher-webhook-fb877d796-xx72r 1/1 Running 0 17h
cattle-turtles-system rancher-clusterctl-configmap-cleanup-t7vlk 0/1 ImagePullBackOff 0 38m
cattle-turtles-system rancher-turtles-controller-manager-6cb8559fb-w2cv8 1/1 Running 144 (6m44s ago) 17h
kube-system coredns-656cc5d5bb-fcgk7 1/1 Running 0 41h
kube-system helm-install-traefik-crd-jlwg7 0/1 Completed 0 41h
kube-system helm-install-traefik-wsp9s 0/1 Completed 2 41h
kube-system local-path-provisioner-86986bc85c-sptdn 1/1 Running 0 41h
kube-system metrics-server-64f5cd9f57-jd9g8 1/1 Running 0 41h
kube-system svclb-traefik-b1de8e61-fd2lw 2/2 Running 0 41h
kube-system svclb-traefik-b1de8e61-pzlvt 2/2 Running 0 41h
kube-system svclb-traefik-b1de8e61-sq6wx 2/2 Running 0 41h
kube-system traefik-768978fdfb-s2fr5 1/1 Running 0 41h
jtxiao@server-01:~$ kubectl describe pod rancher-clusterctl-configmap-cleanup-t7vlk -n cattle-turtles-system
Name: rancher-clusterctl-configmap-cleanup-t7vlk
Namespace: cattle-turtles-system
Priority: 0
Service Account: pre-upgrade-job
Node: server-03/192.168.11.139
Start Time: Thu, 04 Dec 2025 01:16:48 +0000
Labels: batch.kubernetes.io/controller-uid=e0e1d8ed-56ac-4193-a26c-4478da88948c
batch.kubernetes.io/job-name=rancher-clusterctl-configmap-cleanup
controller-uid=e0e1d8ed-56ac-4193-a26c-4478da88948c
job-name=rancher-clusterctl-configmap-cleanup
Annotations: <none>
Status: Pending
IP: 10.42.3.20
IPs:
IP: 10.42.3.20
Controlled By: Job/rancher-clusterctl-configmap-cleanup
Containers:
rancher-clusterctl-configmap-cleanup:
Container ID:
Image: registry.k8s.io/kubernetes/kubectl:v1.32.3
Image ID:
Port: <none>
Host Port: <none>
SeccompProfile: RuntimeDefault
Args:
delete
configmap
--namespace=cattle-turtles-system
clusterctl-config
--ignore-not-found=true
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-jcfvv (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-jcfvv:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
Optional: false
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 39m default-scheduler Successfully assigned cattle-turtles-system/rancher-clusterctl-configmap-cleanup-t7vlk to server-03
Warning Failed 36m (x3 over 39m) kubelet Failed to pull image "registry.k8s.io/kubernetes/kubectl:v1.32.3": failed to pull and unpack image "registry.k8s.io/kubernetes/kubectl:v1.32.3": failed to resolve reference "registry.k8s.io/kubernetes/kubectl:v1.32.3": failed to do request: Head "https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kubernetes/kubectl/manifests/v1.32.3": dial tcp 173.194.202.82:443: connect: connection refused
Normal Pulling 35m (x5 over 39m) kubelet Pulling image "registry.k8s.io/kubernetes/kubectl:v1.32.3"
Warning Failed 35m (x5 over 39m) kubelet Error: ErrImagePull
Warning Failed 35m (x2 over 38m) kubelet Failed to pull image "registry.k8s.io/kubernetes/kubectl:v1.32.3": failed to pull and unpack image "registry.k8s.io/kubernetes/kubectl:v1.32.3": failed to resolve reference "registry.k8s.io/kubernetes/kubectl:v1.32.3": failed to do request: Head "https://us-west2-docker.pkg.dev/v2/k8s-artifacts-prod/images/kubernetes/kubectl/manifests/v1.32.3": dial tcp 74.125.195.82:443: connect: connection refused
Normal BackOff 4m18s (x136 over 39m) kubelet Back-off pulling image "registry.k8s.io/kubernetes/kubectl:v1.32.3"
Warning Failed 4m18s (x136 over 39m) kubelet Error: ImagePullBackOff
说明目前2.13版本，相关的组件国内部署仍然还有部分设置无法被修改。请大佬指正