使用K3S,HELM部署Rancher,WEB无法访问

Rancher Server 设置

  • Rancher 版本:
  • 安装选项 (Helm Chart):
    OS版本:rockylinux9.6

K3S版本:
Client Version: v1.32.3+k3s1
Kustomize Version: v5.5.0
Server Version: v1.32.3+k3s1

Helm版本:
version.BuildInfo{Version:“v3.15.3”, GitCommit:“3bb50bbbdd9c946ba9989fbe4fb4104766302a64”, GitTreeState:“clean”, GoVersion:“go1.22.5”}

cert版本:
v1.14.5

详细部署命令:
部署k3s:
curl -sfL https://rancher-mirror.rancher.cn/k3s/k3s-install.sh |
INSTALL_K3S_VERSION=“v1.32.3+k3s1”
INSTALL_K3S_MIRROR=cn
sh -s -
–system-default-registry “registry.cn-hangzhou.aliyuncs.com

部署cert-manager:
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.crds.yaml

部署rancher:
helm install rancher rancher-latest/rancher
–namespace cattle-system
–set hostname=192.168.60.132.sslip.io
–set replicas=1
–set bootstrapPassword=admin
–set rancherImage=registry.cn-hangzhou.aliyuncs.com/rancher/rancher
–set systemDefaultRegistry=registry.cn-hangzhou.aliyuncs.com
–version 2.12.3

问题描述:
目前已经正常启动,pod也都在running状态,但是web访问不到资源

截图:
image

日志
# POD运行状态:

NAMESPACE                         NAME                                                READY   STATUS      RESTARTS   AGE
cattle-fleet-local-system         fleet-agent-6d8575dc4f-2zrx2                        1/1     Running     0          10h
cattle-fleet-system               fleet-controller-5559b5756c-sx9wj                   3/3     Running     0          10h
cattle-fleet-system               gitjob-58d8d956c9-p9w85                             1/1     Running     0          10h
cattle-fleet-system               helmops-5766cd79b7-89t6r                            1/1     Running     0          10h
cattle-provisioning-capi-system   capi-controller-manager-858db6754b-dc5ct            1/1     Running     0          10h
cattle-system                     rancher-799c88d76-grpsr                             1/1     Running     0          102m
cattle-system                     rancher-webhook-6d55f946b9-mxnn4                    1/1     Running     0          10h
cattle-system                     system-upgrade-controller-dfdf8b78f-gtbjf           1/1     Running     0          10h
cert-manager                      cert-manager-77b74755d9-5kvpr                       1/1     Running     0          11h
cert-manager                      cert-manager-cainjector-65fcfd6ccf-2wt86            1/1     Running     0          11h
cert-manager                      cert-manager-webhook-9b4dd78-q8zzb                  1/1     Running     0          11h
fleet-default                     rke2-machineconfig-cleanup-cronjob-29401445-ml85j   0/1     Completed   0          9h
kube-system                       coredns-5f754ccb4b-snjc8                            1/1     Running     0          11h
kube-system                       helm-install-traefik-crd-2sgmj                      0/1     Completed   0          11h
kube-system                       helm-install-traefik-w6lnk                          0/1     Completed   1          11h
kube-system                       local-path-provisioner-65c47647b6-cs9cf             1/1     Running     0          11h
kube-system                       metrics-server-7d5fccf496-8sgtz                     1/1     Running     0          11h
kube-system                       svclb-traefik-65a6db16-v7c9d                        2/2     Running     0          11h
kube-system                       traefik-6c87bf76ff-xhg4c                            1/1     Running     0          82m

# Ingress 资源
ancher   traefik   192.168.60.132.sslip.io   192.168.60.132   80, 443   12h

#Traefik 状态
traefik          LoadBalancer   10.43.96.6   192.168.60.132   80:30525/TCP,443:30127/TCP   12h
# Rancher 服务
[root@localhost ~]# kubectl get svc -n cattle-system
NAME                       TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
imperative-api-extension   ClusterIP   10.43.199.105   <none>        6666/TCP         11h
rancher                    ClusterIP   10.43.118.90    <none>        80/TCP,443/TCP   12h
rancher-webhook            ClusterIP   10.43.147.30    <none>        443/TCP          11h

# rancher pod 事件
I1126 01:54:13.017573      43 warnings.go:110] "Warning: APIAccess is deprecated in favor of APICatalogItems and ManagedSubscription"
2025/11/26 01:57:24 [INFO] Skipping handler for clusterrepo rancher-charts. NumberOfRetries is 0, MaxRetry is 3, ClusterRepo Generation is 1, ObservedGeneration is 1, LastUpdated plus interval is 2025-11-26 02:47:13 +0000 UTC, now is 2025-11-26 01:57:24.573014454 +0000 UTC
2025/11/26 01:57:34 [INFO] Skipping handler for clusterrepo rancher-charts. NumberOfRetries is 0, MaxRetry is 3, ClusterRepo Generation is 1, ObservedGeneration is 1, LastUpdated plus interval is 2025-11-26 02:47:13 +0000 UTC, now is 2025-11-26 01:57:34.607924253 +0000 UTC
2025/11/26 02:02:30 [INFO] Skipping handler for clusterrepo rancher-charts. NumberOfRetries is 0, MaxRetry is 3, ClusterRepo Generation is 1, ObservedGeneration is 1, LastUpdated plus interval is 2025-11-26 02:47:13 +0000 UTC, now is 2025-11-26 02:02:29.99730186 +0000 UTC
2025/11/26 02:02:40 [INFO] Skipping handler for clusterrepo rancher-charts. NumberOfRetries is 0, MaxRetry is 3, ClusterRepo Generation is 1, ObservedGeneration is 1, LastUpdated plus interval is 2025-11-26 02:47:13 +0000 UTC, now is 2025-11-26 02:02:40.05055191 +0000 UTC
I1126 02:02:55.019134      43 warnings.go:110] "Warning: APIAccess is deprecated in favor of APICatalogItems and ManagedSubscription"

看样子没有任何问题…… 感觉是网络的问题呢

你可以试试在本地 ping 192.168.60.132.sslip.io 看看能否 ping 通,然后在看看 192.168.60.132 的 443 端口是否通

网络和域名都能通,好像是集群的 Ingress 控制器有问题,创建的 Ingress 有问题,我直接通过 NodePort 的方式访问,可以正常访问,没问题了,还没来记得处理Ingress。感谢大佬回复