Docker安装单机版rancher2.14.2失败

Rancher Server 设置

  • Rancher 版本:2.14.2
  • 安装选项 (Docker install/Helm Chart): Docker
    • 如果是 Helm Chart 安装,需要提供 Local 集群的类型(RKE1, RKE2, k3s, EKS, 等)和版本:
  • 在线或离线部署:在线,国内

下游集群信息

  • Kubernetes 版本:
  • Cluster Type (Local/Downstream):
    • 如果 Downstream,是什么类型的集群?(自定义/导入或为托管 等):

用户信息

  • 登录用户的角色是什么? (管理员/集群所有者/集群成员/项目所有者/项目成员/自定义):
    • 如果自定义,自定义权限集:

主机操作系统: rocky 9.6

docker版本: 29.5.3

问题描述: docker安装rancher2.14.2时,多个应用无法启动,rancher-turtles-controller-manager容器报if kind is a CRD, it should be installed before calling Start" err=“no matches for kind "Cluster" in version "cluster.x-k8s.io/v1beta2"” logger=“controller-runtime.source.Kind” kind="Cluster.cluster.x-k8s.io。使用2.14.1版本也是这个问题,请帮看下是什么原因,谢谢

重现步骤:

#配置默认仓库
mkdir -pv /etc/rancher/k3s
cat <<EOF > /etc/rancher/k3s/config.yaml
system-default-registry: registry.cn-hangzhou.aliyuncs.com
EOF

#启动rancher
docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 \
  -v /var/lib/rancher:/var/lib/rancher \
  -v /var/log/rancher/auditlog:/var/log/auditlog \
  -v /etc/localtime:/etc/localtime:ro \
  -v /etc/rancher/k3s/config.yaml:/etc/rancher/k3s/config.yaml \
  --privileged \
  -e CATTLE_SYSTEM_DEFAULT_REGISTRY=registry.cn-hangzhou.aliyuncs.com \
  -e CATTLE_BOOTSTRAP_PASSWORD=rancher \
  --name rancher \
  registry.cn-hangzhou.aliyuncs.com/rancher/rancher:v2.14.2

结果:

sh-4.4# kubectl get pods -A
NAMESPACE               NAME                                                  READY   STATUS             RESTARTS       AGE
cattle-fleet-system     fleet-controller-7cc4664b8b-2gsx8                     3/3     Running            6 (15m ago)    57m
cattle-fleet-system     gitjob-65cff7dcd9-k56wh                               1/1     Running            2 (15m ago)    57m
cattle-fleet-system     helmops-585cf5d55c-8qm2v                              1/1     Running            2 (15m ago)    57m
cattle-system           api-extension-9dc4784f7-kvnwt                         1/1     Running            1 (15m ago)    57m
cattle-system           helm-operation-4gpmg                                  0/2     Error              0              58m
cattle-system           helm-operation-8l6nn                                  0/2     Completed          0              57m
cattle-system           helm-operation-f2ft4                                  0/2     Unknown            0              55m
cattle-system           helm-operation-gl8rg                                  0/2     Unknown            0              57m
cattle-system           helm-operation-s2fck                                  0/2     Unknown            0              54m
cattle-system           helm-operation-srhtm                                  0/2     Error              0              59m
cattle-system           helm-operation-tw48s                                  0/2     Unknown            0              56m
cattle-system           rancher-webhook-647cfd6f-5g8lp                        1/1     Running            2 (15m ago)    56m
cattle-system           system-upgrade-controller-795675cc79-zf8t5            1/1     Running            1 (15m ago)    54m
cattle-turtles-system   rancher-turtles-controller-manager-5b8fc5695c-cw28w   0/1     CrashLoopBackOff   12 (59s ago)   55m
kube-system             coredns-85878d7698-65cjf                              1/1     Running            4 (15m ago)    66m
sh-4.4# 
sh-4.4# 
sh-4.4# crictl images
WARN[0000] Config "/etc/crictl.yaml" does not exist, trying next: "/usr/bin/crictl.yaml" 
WARN[0000] Image connect using default endpoints: [unix:///run/k3s/containerd/containerd.sock unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead. 
IMAGE                                                                 TAG                 IMAGE ID            SIZE
registry.cn-hangzhou.aliyuncs.com/rancher/fleet                       v0.15.2             dd39ecc9fba13       110MB
registry.cn-hangzhou.aliyuncs.com/rancher/mirrored-coredns-coredns    1.14.2              38667dd9be96c       23.3MB
registry.cn-hangzhou.aliyuncs.com/rancher/mirrored-pause              3.6                 6270bb605e12e       301kB
registry.cn-hangzhou.aliyuncs.com/rancher/rancher-webhook             v0.10.6             919366f3a894b       22.3MB
registry.cn-hangzhou.aliyuncs.com/rancher/remotedialer-proxy          v0.7.3              5a233ada9c0fe       18.4MB
registry.cn-hangzhou.aliyuncs.com/rancher/shell                       v0.7.0              48fbc8115d7f0       112MB
registry.cn-hangzhou.aliyuncs.com/rancher/system-upgrade-controller   v0.19.1             7a9d26e5c22c8       14.6MB
registry.cn-hangzhou.aliyuncs.com/rancher/turtles                     v0.26.2             680cc9bee754d       33.8MB

预期结果:

截图:

其他上下文信息:

日志
#rancher-turtles-controller-manager日志
sh-4.4# kubectl logs -n cattle-turtles-system rancher-turtles-controller-manager-5b8fc5695c-cw28w
I0703 04:34:21.039409       1 main.go:234] "enabling Clusterctl Config synchronization controller" logger="setup"
I0703 04:34:21.039472       1 main.go:245] "enabling CAPI Operator synchronization controller" logger="setup"
I0703 04:34:21.046543       1 main.go:254] "enabling UI installation controller" logger="setup"
I0703 04:34:21.046563       1 main.go:176] "starting manager" logger="setup" version="v0.0.0-master+$Format:%H$"
I0703 04:34:21.046633       1 server.go:208] "Starting metrics server" logger="controller-runtime.metrics"
I0703 04:34:21.046655       1 server.go:83] "starting server" name="health probe" addr="[::]:9440"
I0703 04:34:21.046695       1 server.go:247] "Serving metrics server" logger="controller-runtime.metrics" bindAddress=":8080" secure=false
I0703 04:34:21.147056       1 leaderelection.go:257] attempting to acquire leader lease cattle-turtles-system/controller-leader-election-rancher-turtles...
I0703 04:34:38.748215       1 leaderelection.go:271] successfully acquired lease cattle-turtles-system/controller-leader-election-rancher-turtles
I0703 04:34:38.748572       1 controller.go:353] "Starting EventSource" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" source="kind source: *v1.Namespace"
I0703 04:34:38.748673       1 controller.go:353] "Starting EventSource" controller="clusterctlconfig" controllerGroup="turtles-capi.cattle.io" controllerKind="ClusterctlConfig" source="kind source: *v1.ConfigMap"
I0703 04:34:38.748736       1 controller.go:353] "Starting EventSource" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" source="kind source: *v1beta2.Cluster"
I0703 04:34:38.748772       1 controller.go:353] "Starting EventSource" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" source="kind source: *v3.Cluster"
I0703 04:34:38.748843       1 controller.go:353] "Starting EventSource" controller="cleanup" controllerGroup="management.cattle.io" controllerKind="Cluster" source="kind source: *v3.Cluster"
I0703 04:34:38.748982       1 controller.go:353] "Starting EventSource" controller="healthcheck-turtles-capi.cattle.io/v1alpha1, Kind=CAPIProvider" controllerGroup="apps" controllerKind="Deployment" source="kind source: *v1alpha1.CAPIProvider"
I0703 04:34:38.749038       1 controller.go:353] "Starting EventSource" controller="clusterctlconfig" controllerGroup="turtles-capi.cattle.io" controllerKind="ClusterctlConfig" source="kind source: *v1alpha1.ClusterctlConfig"
I0703 04:34:38.749321       1 controller.go:353] "Starting EventSource" controller="ProviderReconciler" controllerGroup="turtles-capi.cattle.io" controllerKind="CAPIProvider" source="kind source: *v1alpha1.CAPIProvider"
I0703 04:34:38.749370       1 controller.go:353] "Starting EventSource" controller="healthcheck-turtles-capi.cattle.io/v1alpha1, Kind=CAPIProvider" controllerGroup="apps" controllerKind="Deployment" source="kind source: *v1.Deployment"
I0703 04:34:38.749414       1 controller.go:353] "Starting EventSource" controller="ProviderReconciler" controllerGroup="turtles-capi.cattle.io" controllerKind="CAPIProvider" source="kind source: *v1alpha1.CAPIProvider"
I0703 04:34:38.749420       1 controller.go:353] "Starting EventSource" controller="ProviderReconciler" controllerGroup="turtles-capi.cattle.io" controllerKind="CAPIProvider" source="kind source: *v1.Secret"
E0703 04:34:38.752995       1 kind.go:75] "if kind is a CRD, it should be installed before calling Start" err="no matches for kind \"Cluster\" in version \"cluster.x-k8s.io/v1beta2\"" logger="controller-runtime.source.Kind" kind="Cluster.cluster.x-k8s.io"
I0703 04:34:38.849405       1 controller.go:286] "Starting Controller" controller="clusterctlconfig" controllerGroup="turtles-capi.cattle.io" controllerKind="ClusterctlConfig"
I0703 04:34:38.849456       1 controller.go:289] "Starting workers" controller="clusterctlconfig" controllerGroup="turtles-capi.cattle.io" controllerKind="ClusterctlConfig" worker count=1
I0703 04:34:38.849497       1 controller.go:286] "Starting Controller" controller="cleanup" controllerGroup="management.cattle.io" controllerKind="Cluster"
I0703 04:34:38.849503       1 controller.go:289] "Starting workers" controller="cleanup" controllerGroup="management.cattle.io" controllerKind="Cluster" worker count=1
I0703 04:34:38.851244       1 config.go:152] "Turtles configured to use Rancher default registry for images" controller="clusterctlconfig" controllerGroup="turtles-capi.cattle.io" controllerKind="ClusterctlConfig" ClusterctlConfig="cattle-turtles-system/clusterctl-config" namespace="cattle-turtles-system" name="clusterctl-config" reconcileID="4b275bab-3d98-4c83-9b22-873a501825fb"
I0703 04:34:38.952257       1 config.go:162] "Rancher default registry has been set" controller="clusterctlconfig" controllerGroup="turtles-capi.cattle.io" controllerKind="ClusterctlConfig" ClusterctlConfig="cattle-turtles-system/clusterctl-config" namespace="cattle-turtles-system" name="clusterctl-config" reconcileID="4b275bab-3d98-4c83-9b22-873a501825fb" registry="registry.cn-hangzhou.aliyuncs.com"
I0703 04:34:38.952291       1 config.go:177] "Overridden provider image to use Rancher default registry" controller="clusterctlconfig" controllerGroup="turtles-capi.cattle.io" controllerKind="ClusterctlConfig" ClusterctlConfig="cattle-turtles-system/clusterctl-config" namespace="cattle-turtles-system" name="clusterctl-config" reconcileID="4b275bab-3d98-4c83-9b22-873a501825fb" image="cluster-api" repository="registry.cn-hangzhou.aliyuncs.com/rancher" tag=""
I0703 04:34:38.954487       1 controller.go:286] "Starting Controller" controller="ProviderReconciler" controllerGroup="turtles-capi.cattle.io" controllerKind="CAPIProvider"
I0703 04:34:38.954505       1 controller.go:289] "Starting workers" controller="ProviderReconciler" controllerGroup="turtles-capi.cattle.io" controllerKind="CAPIProvider" worker count=1
I0703 04:34:38.956521       1 controller.go:286] "Starting Controller" controller="healthcheck-turtles-capi.cattle.io/v1alpha1, Kind=CAPIProvider" controllerGroup="apps" controllerKind="Deployment"
I0703 04:34:38.956537       1 controller.go:289] "Starting workers" controller="healthcheck-turtles-capi.cattle.io/v1alpha1, Kind=CAPIProvider" controllerGroup="apps" controllerKind="Deployment" worker count=1
E0703 04:34:48.751214       1 kind.go:75] "if kind is a CRD, it should be installed before calling Start" err="no matches for kind \"Cluster\" in version \"cluster.x-k8s.io/v1beta2\"" logger="controller-runtime.source.Kind" kind="Cluster.cluster.x-k8s.io"
E0703 04:34:58.751095       1 kind.go:75] "if kind is a CRD, it should be installed before calling Start" err="no matches for kind \"Cluster\" in version \"cluster.x-k8s.io/v1beta2\"" logger="controller-runtime.source.Kind" kind="Cluster.cluster.x-k8s.io"
E0703 04:35:08.750490       1 kind.go:75] "if kind is a CRD, it should be installed before calling Start" err="no matches for kind \"Cluster\" in version \"cluster.x-k8s.io/v1beta2\"" logger="controller-runtime.source.Kind" kind="Cluster.cluster.x-k8s.io"

日志的意思大概是 turtles 启动依赖 Cluster(cluster.x-k8s.io/v1beta2)资源,所以一直没启动,你还得向上查找其他的日志,挨个用 kubectl logs helm-operation-xxxx 看看,也许会有那种很明确的日志提示,我用你的命令,在我本地没重现。

这是所有helm-operation-xxxx的日志

sh-4.4# kubectl get pods -A
NAMESPACE               NAME                                                  READY   STATUS             RESTARTS      AGE
cattle-fleet-system     fleet-controller-7cc4664b8b-w8sj5                     3/3     Running            0             18m
cattle-fleet-system     gitjob-65cff7dcd9-6t4hf                               1/1     Running            0             18m
cattle-fleet-system     helmops-585cf5d55c-p8xsb                              1/1     Running            0             18m
cattle-system           api-extension-9dc4784f7-jm99f                         1/1     Running            0             18m
cattle-system           helm-operation-2blrx                                  0/2     Unknown            0             27m
cattle-system           helm-operation-4cwmk                                  0/2     Completed          0             28m
cattle-system           helm-operation-4lnvx                                  0/2     Error              0             26m
cattle-system           helm-operation-b5jn8                                  0/2     Error              0             18m
cattle-system           helm-operation-bqqft                                  0/2     Error              0             24m
cattle-system           helm-operation-f4zdf                                  0/2     Unknown            0             14m
cattle-system           helm-operation-fwd8m                                  0/2     Unknown            0             15m
cattle-system           helm-operation-js4dg                                  0/2     Error              0             25m
cattle-system           helm-operation-kv6pv                                  0/2     Unknown            0             18m
cattle-system           helm-operation-mkktl                                  0/2     Error              0             23m
cattle-system           helm-operation-n96s4                                  0/2     Error              0             22m
cattle-system           helm-operation-trq44                                  0/2     Error              0             20m
cattle-system           helm-operation-tzdgh                                  0/2     Error              0             21m
cattle-system           helm-operation-vj72t                                  0/2     Error              0             29m
cattle-system           helm-operation-wz256                                  0/2     Unknown            0             17m
cattle-system           rancher-webhook-647cfd6f-45f75                        1/1     Running            0             16m
cattle-system           system-upgrade-controller-795675cc79-c5kcq            1/1     Running            0             15m
cattle-turtles-system   rancher-turtles-controller-manager-5b8fc5695c-vhhmt   0/1     CrashLoopBackOff   2 (8s ago)    14m
kube-system             coredns-85878d7698-ttjtw                              1/1     Running            3 (13m ago)   30m
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-2blrx
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --values=/home/shell/helm/values-fleet-109.0.2-up0.15.2.yaml --version=109.0.2+up0.15.2 --wait=true fleet /home/shell/helm/fleet-109.0.2-up0.15.2.tgz
Release "fleet" does not exist. Installing it now.
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-4cwmk
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --version=109.0.2+up0.15.2 --wait=true fleet-crd /home/shell/helm/fleet-crd-109.0.2-up0.15.2.tgz
Release "fleet-crd" does not exist. Installing it now.
NAME: fleet-crd
LAST DEPLOYED: Mon Jul  6 05:48:41 2026
NAMESPACE: cattle-fleet-system
STATUS: deployed
REVISION: 1
TEST SUITE: None

---------------------------------------------------------------------
SUCCESS: helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --version=109.0.2+up0.15.2 --wait=true fleet-crd /home/shell/helm/fleet-crd-109.0.2-up0.15.2.tgz
---------------------------------------------------------------------
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-4lnvx
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --version=109.0.2+up0.15.2 --wait=true fleet-crd /home/shell/helm/fleet-crd-109.0.2-up0.15.2.tgz
Release "fleet-crd" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-b5jn8
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --values=/home/shell/helm/values-fleet-109.0.2-up0.15.2.yaml --version=109.0.2+up0.15.2 --wait=true fleet /home/shell/helm/fleet-109.0.2-up0.15.2.tgz
Release "fleet" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-bqqft
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --values=/home/shell/helm/values-fleet-109.0.2-up0.15.2.yaml --version=109.0.2+up0.15.2 --wait=true fleet /home/shell/helm/fleet-109.0.2-up0.15.2.tgz
Release "fleet" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-f4zdf
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-turtles-system --reset-values=true --timeout=5m0s --values=/home/shell/helm/values-rancher-turtles-109.0.2-up0.26.2.yaml --version=109.0.2+up0.26.2 --wait=true rancher-turtles /home/shell/helm/rancher-turtles-109.0.2-up0.26.2.tgz
Release "rancher-turtles" does not exist. Installing it now.
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-fwd8m
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-system --reset-values=true --timeout=5m0s --values=/home/shell/helm/values-system-upgrade-controller-109.0.1.yaml --version=109.0.1 --wait=true system-upgrade-controller /home/shell/helm/system-upgrade-controller-109.0.1.tgz
Release "system-upgrade-controller" does not exist. Installing it now.
I0706 05:50:52.269963      27 warnings.go:107] "Warning: spec.template.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution[1].preference.matchExpressions[0].key: node-role.kubernetes.io/master is use \"node-role.kubernetes.io/control-plane\" instead"
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-js4dg
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --values=/home/shell/helm/values-fleet-109.0.2-up0.15.2.yaml --version=109.0.2+up0.15.2 --wait=true fleet /home/shell/helm/fleet-109.0.2-up0.15.2.tgz
Release "fleet" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-kv6pv
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-system --reset-values=true --timeout=5m0s --values=/home/shell/helm/values-remotedialer-proxy-109.0.3-up0.7.3.yaml --version=109.0.3+up0.7.3 --wait=true remotedialer-proxy /home/shell/helm/remotedialer-proxy-109.0.3-up0.7.3.tgz
Release "remotedialer-proxy" does not exist. Installing it now.
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-mkktl
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --version=109.0.2+up0.15.2 --wait=true fleet-crd /home/shell/helm/fleet-crd-109.0.2-up0.15.2.tgz
Release "fleet-crd" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-n96s4
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --values=/home/shell/helm/values-fleet-109.0.2-up0.15.2.yaml --version=109.0.2+up0.15.2 --wait=true fleet /home/shell/helm/fleet-109.0.2-up0.15.2.tgz
Release "fleet" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-trq44
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --values=/home/shell/helm/values-fleet-109.0.2-up0.15.2.yaml --version=109.0.2+up0.15.2 --wait=true fleet /home/shell/helm/fleet-109.0.2-up0.15.2.tgz
Release "fleet" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-tzdgh
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --version=109.0.2+up0.15.2 --wait=true fleet-crd /home/shell/helm/fleet-crd-109.0.2-up0.15.2.tgz
Release "fleet-crd" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-vj72t
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-fleet-system --reset-values=true --take-ownership=true --timeout=5m0s --values=/home/shell/helm/values-fleet-109.0.2-up0.15.2.yaml --version=109.0.2+up0.15.2 --wait=true fleet /home/shell/helm/fleet-109.0.2-up0.15.2.tgz
Release "fleet" does not exist. Installing it now.
Error: release: already exists
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# 
sh-4.4# kubectl logs -n cattle-system helm-operation-wz256
Defaulted container "helm" out of: helm, proxy, init-kubeconfig-volume (init)
helm upgrade --history-max=5 --install=true --labels=catalog.cattle.io/cluster-repo-name=rancher-charts --namespace=cattle-system --reset-values=true --take-ownership=true --timeout=5m0s --values=/home/shell/helm/values-rancher-webhook-109.0.2-up0.10.6.yaml --version=109.0.2+up0.10.6 --wait=true rancher-webhook /home/shell/helm/rancher-webhook-109.0.2-up0.10.6.tgz
Release "rancher-webhook" does not exist. Installing it now.

你在多等等,有时候是因为镜像没拉下来导致的

这个测试过很多遍,中间等待时间都有超过三四个小时,一直没恢复。感觉是在拉取这两个镜像registry.cn-hangzhou.aliyuncs.com/rancher/fleet-agent,registry.cn-hangzhou.aliyuncs.com/rancher/cluster-api-controller之前卡住了。

昨天在AI的提示下,在rancher容器里创建了x-k8s.io相关CRD,又在UI界面删除部署失败的应用等一系列操作后,等待一晚上,今天早上上班发现状态恢复正常。

不知道和操作系统有关系没有,我使用的操作系统是rocky9.6。

我再测试下使用rke2集群搭建rancher,如果这个测试没问题,打算使用这个方案,感谢