国内ECS无法创建的创建的REK2集群 rancher版本:v2.8.4

无法正常安装的集群


长时间这个状态

rancher-server端日志报错:
oller-manager, kube-scheduler
2025/03/16 10:48:28 [ERROR] error syncing ‘c-m-2lvjvmcp’: handler cluster-deploy: cluster context c-m-2lvjvmcp is unavailable, requeuing
2025/03/16 10:48:28 [INFO] [planner] rkecluster fleet-default/weile: configuring bootstrap node(s) custom-c143de4dc205: waiting for probes: calico, kube-controller-manager, kube-scheduler
W0316 10:48:28.574222 39 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineSet is deprecated; use cluster.x-k8s.io/v1beta1 MachineSet
2025/03/16 10:48:43 [ERROR] error syncing ‘all’: handler user-controllers-controller: userControllersController: failed to set peers for key all: failed to start user controllers for cluster c-m-2lvjvmcp: ClusterUnavailable 503: cluster not found, requeuing
2025/03/16 10:48:58 [ERROR] error syncing ‘c-m-2lvjvmcp’: handler cluster-deploy: cluster context c-m-2lvjvmcp is unavailable, requeuing
2025/03/16 10:48:58 [INFO] [planner] rkecluster fleet-default/weile: configuring bootstrap node(s) custom-c143de4dc205: waiting for probes: calico, kube-controller-manager, kube-scheduler
2025/03/16 10:49:47 [ERROR] Error during subscribe websocket: close sent
W0316 10:49:50.311616 39 warnings.go:80] cluster.x-k8s.io/v1alpha3 Machine is deprecated; use cluster.x-k8s.io/v1beta1 Machine
W0316 10:50:22.158408 39 warnings.go:80] cluster.x-k8s.io/v1alpha3 MachineHealthCheck is deprecated; use cluster.x-k8s.io/v1beta1 MachineHealthCheck
2025/03/16 10:50:43 [ERROR] error syncing ‘all’: handler user-controllers-controller: userControllersController: failed to set peers for key all: failed to start user controllers for cluster c-m-2lvjvmcp: ClusterUnavailable 503: cluster not found, requeuing
2025/03/16 10:50:58 [ERROR] error syncing ‘c-m-2lvjvmcp’: handler cluster-deploy: cluster context c-m-2lvjvmcp is unavailable, requeuing
2025/03/16 10:50:58 [INFO] [planner] rkecluster fleet-default/weile: configuring bootstrap node(s) custom-c143de4dc205: waiting for probes: calico, kube-controller-manager, kube-scheduler
2025/03/16 10:51:24 [ERROR] Error during subscribe websocket: close sent
2025/03/16 10:52:26 [ERROR] Error during subscribe websocket: close sent
2025/03/16 10:52:27 [INFO] [planner] rkecluster fleet-default/weile: configuring bootstrap node(s) custom-c143de4dc205: waiting for probes: calico, kube-controller-manager, kube-scheduler
2025/03/16 10:52:43 [ERROR] error syncing ‘all’: handler user-controllers-controller: userControllersController: failed to set peers for key all: failed to start user controllers for cluster c-m-2lvjvmcp: ClusterUnavailable 503: cluster not found, requeuing
2025/03/16 10:52:58 [ERROR] error syncing ‘c-m-2lvjvmcp’: handler cluster-deploy: cluster context c-m-2lvjvmcp is unavailable, requeuing
2025/03/16 10:52:58 [INFO] [planner] rkecluster fleet-default/weile: configuring bootstrap node(s) custom-c143de4dc205: waiting for probes: calico, kube-controller-manager, kube-scheduler
W0316 10:53:50.553365 39 warnings.go:80] cluster.x-k8s.io/v1alpha3 Cluster is deprecated; use cluster.x-k8s.io/v1beta1 Cluster

按照默认的话题模版重新提交下吧,现在这样缺少上下文

感谢,已经解决了,主要是的master节点资源不足导致,但是rancher中server中日志一直显示watting各个组件创建,不是很友好。

从rancher当中下载的kubeConfig文件不能用:


这个怎么回事呢?

并且按照:Rancher的普通用户如何使用kubectl从外部访问集群 - #2,来自 ksd
您说的创建test用户的方式的创建创建了一个用户下载的config文件还是不行

你把详细的操作步骤都列出来吧,包括注册节点的地址,rancher server 的地址等等,按照模版