安装 Kubesphere3.1.0 成功后无法访问 console 页面
- 已编辑
Cauchy
现在已经安装成功，提示我访问 30880 的 web 端
但是访问不了，连接超时是为什么呢
用 telnet 能够连接的上，服务器资源也还够 CPU 使用了 6%，内存只用了 2G
我服务器有 16G 内存，6核 CPU，120G 硬盘
防火墙已经全部关闭 telnet 可以访问 curl 访问不了
pod 信息
NAME READY STATUS RESTARTS AGE
ks-apiserver-7d4f466f75-5wc5v 1/1 Running 0 29m
ks-console-5576fccbb8-4mqpt 1/1 Running 0 20h
ks-controller-manager-7d9b98f467-r2km6 1/1 Running 0 29m
ks-installer-8d7b5cfc4-lkffh 1/1 Running 0 32mNAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-kube-controllers-8545b68dd4-8bzjr 1/1 Running 0 22h 10.233.90.1 node1 <none> <none>
kube-system calico-node-bhf2k 1/1 Running 0 22h 192.168.113.121 node1 <none> <none>
kube-system calico-node-k2r5k 1/1 Running 1 22h 192.168.113.120 master1 <none> <none>
kube-system calico-node-t7dbs 1/1 Running 0 22h 192.168.113.122 node2 <none> <none>
kube-system coredns-867b49865c-krk2l 1/1 Running 1 22h 10.233.97.5 master1 <none> <none>
kube-system coredns-867b49865c-txt7n 1/1 Running 1 22h 10.233.97.4 master1 <none> <none>
kube-system init-pvc-1dcd1a64-38c6-4250-8043-1f91ccc025a5 0/1 Completed 0 17h 10.233.96.4 node2 <none> <none>
kube-system init-pvc-c6e7bfc1-5485-4a59-89d8-691015562d39 0/1 Completed 0 17h 10.233.90.8 node1 <none> <none>
kube-system kube-apiserver-master1 1/1 Running 2 22h 192.168.113.120 master1 <none> <none>
kube-system kube-controller-manager-master1 1/1 Running 6 22h 192.168.113.120 master1 <none> <none>
kube-system kube-proxy-dj8nx 1/1 Running 1 22h 192.168.113.120 master1 <none> <none>
kube-system kube-proxy-mqmgw 1/1 Running 0 22h 192.168.113.121 node1 <none> <none>
kube-system kube-proxy-qhxwt 1/1 Running 0 22h 192.168.113.122 node2 <none> <none>
kube-system kube-scheduler-master1 1/1 Running 5 22h 192.168.113.120 master1 <none> <none>
kube-system nodelocaldns-bkdlp 1/1 Running 0 22h 192.168.113.122 node2 <none> <none>
kube-system nodelocaldns-rsdn6 1/1 Running 0 22h 192.168.113.121 node1 <none> <none>
kube-system nodelocaldns-xkl8q 1/1 Running 1 22h 192.168.113.120 master1 <none> <none>
kube-system openebs-localpv-provisioner-c46f4fbd5-ntkw8 1/1 Running 57 20h 10.233.96.1 node2 <none> <none>
kube-system snapshot-controller-0 1/1 Running 0 20h 10.233.96.2 node2 <none> <none>
kubesphere-controls-system default-http-backend-76d9fb4bb7-pkkl7 1/1 Running 0 20h 10.233.90.4 node1 <none> <none>
kubesphere-controls-system kubectl-admin-7b69cb97d5-6brvg 1/1 Running 0 13h 10.233.90.12 node1 <none> <none>
kubesphere-monitoring-system alertmanager-main-0 2/2 Running 0 17h 10.233.90.9 node1 <none> <none>
kubesphere-monitoring-system alertmanager-main-1 2/2 Running 0 17h 10.233.96.5 node2 <none> <none>
kubesphere-monitoring-system alertmanager-main-2 2/2 Running 0 17h 10.233.96.6 node2 <none> <none>
kubesphere-monitoring-system kube-state-metrics-687c7c4d86-nb4d4 3/3 Running 2 17h 10.233.90.7 node1 <none> <none>
kubesphere-monitoring-system node-exporter-525tt 2/2 Running 0 17h 192.168.113.121 node1 <none> <none>
kubesphere-monitoring-system node-exporter-7dqgb 2/2 Running 0 17h 192.168.113.122 node2 <none> <none>
kubesphere-monitoring-system node-exporter-vgrhq 2/2 Running 0 17h 192.168.113.120 master1 <none> <none>
kubesphere-monitoring-system notification-manager-deployment-7bd887ffb4-pwjg8 1/1 Running 0 13h 10.233.90.13 node1 <none> <none>
kubesphere-monitoring-system notification-manager-deployment-7bd887ffb4-vxhrp 1/1 Running 0 13h 10.233.96.8 node2 <none> <none>
kubesphere-monitoring-system notification-manager-operator-78595d8666-d9vfn 2/2 Running 1 13h 10.233.90.11 node1 <none> <none>
kubesphere-monitoring-system prometheus-k8s-0 0/3 Pending 0 17h <none> <none> <none> <none>
kubesphere-monitoring-system prometheus-k8s-1 0/3 Pending 0 17h <none> <none> <none> <none>
kubesphere-monitoring-system prometheus-operator-d7fdfccbf-7p2pv 2/2 Running 0 17h 10.233.96.3 node2 <none> <none>
kubesphere-system ks-apiserver-7d4f466f75-5wc5v 1/1 Running 0 29m 10.233.97.8 master1 <none> <none>
kubesphere-system ks-console-5576fccbb8-4mqpt 1/1 Running 0 20h 10.233.90.3 node1 <none> <none>
kubesphere-system ks-controller-manager-7d9b98f467-r2km6 1/1 Running 0 29m 10.233.97.9 master1 <none> <none>
kubesphere-system ks-installer-8d7b5cfc4-lkffh 1/1 Running 0 33m 10.233.90.15 node1 <none> <none>- 已编辑
重装了一次，成功了但还是访问不了，都是 telnet 可以 curl 不可以
Cauchy @Jeff
#####################################################
### Welcome to KubeSphere! ###
#####################################################
Console: http://192.168.113.120:30880
Account: admin
Password: P@88w0rd
NOTES：
1. After you log into the console, please check the
monitoring status of service components in
"Cluster Management". If any service is not
ready, please wait patiently until all components
are up and running.
2. Please change the default password after login.
#####################################################
https://kubesphere.io 2021-05-11 12:06:41
#####################################################pod 信息
[root@master1 kubesphere]# kubectl get pods -n kubesphere-system
NAME READY STATUS RESTARTS AGE
ks-apiserver-75958c7c85-wqdkr 1/1 Running 0 27m
ks-console-5576fccbb8-ssgqs 1/1 Running 0 29m
ks-controller-manager-fb858c67b-gsv29 1/1 Running 3 27m
ks-installer-7fb74c656c-8887s 1/1 Running 0 34m
minio-f69748945-j7qhm 1/1 Running 0 31m
openldap-0 1/1 Running 1 31m
openpitrix-import-job-kc22l 0/1 Completed 0 29m
redis-658988fc5b-rfnnf 1/1 Running 0 32m
`clusterconfiguration.installer.kubesphere.io/ks-installer unchanged
WARN[17:35:42 HKT] Task failed …
WARN[17:35:42 HKT] error: KubeSphere startup timeout.
Error: Failed to deploy kubesphere: KubeSphere startup timeout.
Usage:
kk create cluster [flags]
Flags:
–download-cmd string The user defined command to download the necessary binary files. The first param ‘%s’ is output path, the second param ‘%s’, is the URL (default “curl -L -o %s %s”)
-f, –filename string Path to a configuration file
-h, –help help for cluster
–skip-pull-images Skip pre pull images
–with-kubernetes string Specify a supported version of kubernetes (default “v1.19.8”)
–with-kubesphere Deploy a specific version of kubesphere (default v3.1.0)
–with-local-storage Deploy a local PV provisioner
-y, –yes Skip pre-check of the installation
Global Flags:
–debug Print detailed information (default true)
–in-cluster Running inside the cluster
Failed to deploy kubesphere: KubeSphere startup timeout.`
同样的问题 Failed to deploy kubesphere: KubeSphere startup timeout.
我也是，怎么解决的呢
是否被防火墙拦住了，看看防火墙关了没
- 已编辑
可能是内存不足，重启一下docker试试
leons9th 我也是telnet 可以 curl 不可以，怎么解决的啊
我也是呀，这个问题很奇怪，但如果重装启动，就报其他错误