Rancher Server 设置
- Rancher 版本： [v2.14.2]
- 安装选项 (Docker install/Helm Chart):
- 如果是 Helm Chart 安装，需要提供 Local 集群的类型（RKE1, RKE2, k3s, EKS, 等）和版本：Helm Chart，kubeadmin安装的集群
- 在线或离线部署：离线
下游集群信息
- Kubernetes 版本: 1.26.15
- Cluster Type (Local/Downstream):
- 如果 Downstream，是什么类型的集群?(自定义/导入或为托管 等): 导入
用户信息
- 登录用户的角色是什么？ （管理员/集群所有者/集群成员/项目所有者/项目成员/自定义）：admin
- 如果自定义，自定义权限集：
**主机操作系统：麒麟v10 sp2（ky10.aarch64）
**问题描述：rancher部署在v1.32.9的k8s集群中，想加入已有的一个集群，集群版本是1.26.15，但是agent日志显示连接成功，ui控制上显示agent未连接
**截图：
其他上下文信息：
日志
[root@k8s-master-201 ~]# kubectl logs -n cattle-system -l app=cattle-cluster-agent --tail=80
INFO: Environment: CATTLE_ADDRESS=10.48.74.188 CATTLE_CA_CHECKSUM=cd427d0aec57e87cc7505075f448464c975e7aca82252dd3f34dfe4fc0ae2c06 CATTLE_CLUSTER=true CATTLE_CLUSTER_AGENT_PORT=tcp://10.96.80.145:80 CATTLE_CLUSTER_AGENT_PORT_443_TCP=tcp://10.96.80.145:443 CATTLE_CLUSTER_AGENT_PORT_443_TCP_ADDR=10.96.80.145 CATTLE_CLUSTER_AGENT_PORT_443_TCP_PORT=443 CATTLE_CLUSTER_AGENT_PORT_443_TCP_PROTO=tcp CATTLE_CLUSTER_AGENT_PORT_80_TCP=tcp://10.96.80.145:80 CATTLE_CLUSTER_AGENT_PORT_80_TCP_ADDR=10.96.80.145 CATTLE_CLUSTER_AGENT_PORT_80_TCP_PORT=80 CATTLE_CLUSTER_AGENT_PORT_80_TCP_PROTO=tcp CATTLE_CLUSTER_AGENT_SERVICE_HOST=10.96.80.145 CATTLE_CLUSTER_AGENT_SERVICE_PORT=80 CATTLE_CLUSTER_AGENT_SERVICE_PORT_HTTP=80 CATTLE_CLUSTER_AGENT_SERVICE_PORT_HTTPS_INTERNAL=443 CATTLE_CLUSTER_REGISTRY=docker.1ms.run CATTLE_CREDENTIAL_NAME=cattle-credentials-5314b74af0 CATTLE_INGRESS_IP_DOMAIN=sslip.io CATTLE_INSTALL_UUID=a83dd1ad-9ed6-4500-a8a9-86ec60616d61 CATTLE_INTERNAL_ADDRESS= CATTLE_K8S_MANAGED=true CATTLE_NODE_NAME=cattle-cluster-agent-549db69b65-xvx69 CATTLE_RANCHER_TURTLES_VERSION=109.0.2+up0.26.2 CATTLE_RANCHER_WEBHOOK_VERSION=109.0.2+up0.10.6 CATTLE_SERVER=https://rancher.dikong.com CATTLE_SERVER_VERSION=v2.14.2 CATTLE_SUC_APP_NAME_OVERRIDE=
INFO: Using resolv.conf: search cattle-system.svc.cluster.local svc.cluster.local cluster.local nameserver 10.96.0.10 options ndots:5
INFO: https://rancher.dikong.com/ping is accessible
INFO: rancher.dikong.com resolves to 192.168.110.2
INFO: Value from https://rancher.dikong.com/v3/settings/cacerts is an x509 certificate
time="2026-08-12T03:55:03Z" level=info msg="starting cattle-credential-cleanup goroutine in the background"
time="2026-08-12T03:55:03Z" level=info msg="Listening on /tmp/log.sock"
time="2026-08-12T03:55:03Z" level=info msg="Rancher agent version v2.14.2 is starting"
time="2026-08-12T03:55:03Z" level=info msg="Testing connection to https://rancher.dikong.com using trusted certificate authorities within: /etc/kubernetes/ssl/certs/serverca"
time="2026-08-12T03:55:03Z" level=info msg="Connecting to wss://rancher.dikong.com/v3/connect/register with token starting with rvqcnjh5wm2h8b5h7wzklzzzz8h"
time="2026-08-12T03:55:03Z" level=info msg="Connecting to proxy" url="wss://rancher.dikong.com/v3/connect/register"
time="2026-08-12T03:55:03Z" level=info msg="Connected to proxy" url="wss://rancher.dikong.com/v3/connect/register"