创建部署问题时,请参考下面模板,你提供的信息越多,越容易及时获得解答。如果未按模板创建问题,管理员有权关闭问题。
确保帖子格式清晰易读,用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题,不能指望别人花上半个小时给你解答。

操作系统信息
macos intel

Kubernetes版本信息
v1.22.12

容器运行时
➜  ~ docker version

Client:

Cloud integration: v1.0.28

Version:           20.10.17

API version:       1.41

Go version:        go1.17.11

Git commit:        100c701

Built:             Mon Jun  6 23:04:45 2022

OS/Arch:           darwin/amd64

Context:           default

Experimental:      true

Server: Docker Desktop 4.11.1 (84025)

Engine:

Version:          20.10.17

API version:      1.41 (minimum version 1.12)

Go version:       go1.17.11

Git commit:       a89b842

Built:            Mon Jun  6 23:01:23 2022

OS/Arch:          linux/amd64

Experimental:     false

containerd:

Version:          1.6.6

GitCommit:        10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1

runc:

Version:          1.1.2

GitCommit:        v1.1.2-0-ga916309

docker-init:

Version:          0.19.0

GitCommit:        de40ad0

KubeSphere版本信息
3.3.2

问题是什么
#####################################################

###              Welcome to KubeSphere!           ###

#####################################################

Console: http://: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             2023-05-06 02:29:03

#####################################################

➜  ~ kubectl get pod -n kubesphere-system

NAME                                    READY   STATUS    RESTARTS   AGE

ks-apiserver-576fbd5df4-hv4s4           1/1     Running   0          23m

ks-console-5c9fcbc67b-tn86l             1/1     Running   0          23m

ks-controller-manager-f8dfd55c8-hbdvc   1/1     Running   0          23m

ks-installer-846c78ddbf-mf49q           1/1     Running   0          30m

成功安装后,pod也正常,无法登入WEB界面控制台

    qczrzl 无法登入

    ➜  ~ kubectl get pod -A   

    NAMESPACE                      NAME                                               READY   STATUS    RESTARTS   AGE

    kube-system                    coredns-6f6b8cc4f6-rw746                           1/1     Running   0          19m

    kube-system                    etcd-minikube                                      1/1     Running   0          20m

    kube-system                    kube-apiserver-minikube                            1/1     Running   0          20m

    kube-system                    kube-controller-manager-minikube                   1/1     Running   0          20m

    kube-system                    kube-proxy-8tm6v                                   1/1     Running   0          19m

    kube-system                    kube-scheduler-minikube                            1/1     Running   0          20m

    kube-system                    snapshot-controller-0                              1/1     Running   0          16m

    kube-system                    storage-provisioner                                1/1     Running   1          20m

    kubesphere-controls-system     default-http-backend-5bf68ff9b8-zk8vx              1/1     Running   0          15m

    kubesphere-controls-system     kubectl-admin-6667774bb-7tpmg                      1/1     Running   0          8m9s

    kubesphere-monitoring-system   alertmanager-main-0                                2/2     Running   0          12m

    kubesphere-monitoring-system   kube-state-metrics-687d66b747-hrbmz                3/3     Running   0          12m

    kubesphere-monitoring-system   node-exporter-7vmf7                                2/2     Running   0          12m

    kubesphere-monitoring-system   notification-manager-deployment-78664576cb-zmttt   2/2     Running   0          6m29s

    kubesphere-monitoring-system   notification-manager-operator-7d44854f54-bf5tj     2/2     Running   0          11m

    kubesphere-monitoring-system   prometheus-k8s-0                                   2/2     Running   0          12m

    kubesphere-monitoring-system   prometheus-operator-8955bbd98-48cfq                2/2     Running   0          12m

    kubesphere-system              ks-apiserver-576fbd5df4-cz7cn                      1/1     Running   0          15m

    kubesphere-system              ks-console-5c9fcbc67b-vqk7v                        1/1     Running   0          15m

    kubesphere-system              ks-controller-manager-f8dfd55c8-6v24q              1/1     Running   0          15m

    kubesphere-system              ks-installer-846c78ddbf-kbl9v                      1/1     Running   0          18m

    ➜  ~ kubectl get svc -n kubesphere-system

    NAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE

    ks-apiserver            ClusterIP   10.105.118.0     <none>        80/TCP         15m

    ks-console              NodePort    10.109.154.51    <none>        80:30880/TCP   15m

    ks-controller-manager   ClusterIP   10.104.123.182   <none>        443/TCP        15m

    ➜  ~ netstat -AaLlnW|grep 30880          

    ➜  ~ netstat -AaLlnW|grep 80   

    df7d1f876e93f4d7        0 0/0/128        127.0.0.1.1080         

    df7d1f87464d1957        0 0/0/80         *.3306   

    这边看本地service 的端口都没监听,大佬有遇到过吗

    sicheng43 netstat中看不到端口是正常的,你看看相关pod日志kubectl -n kubesphere-system logs -l app=ks-controller-manager

      qczrzl ➜  ~ kubectl -n kubesphere-system logs -l app=ks-controller-manager

      I0506 06:54:02.166744       1 event.go:282] Event(v1.ObjectReference{Kind:“ClusterRoleBinding”, Namespace:"", Name:“kubeadm:kubelet-bootstrap”, UID:“49583fe9-36b6-4956-ae7d-aaa099836e05”, APIVersion:“rbac.authorization.k8s.io/v1”, ResourceVersion:“236”, FieldPath:""}): type: ‘Normal’ reason: ‘Synced’ ClusterRoleBinding synced successfully

      I0506 06:54:02.166761       1 event.go:282] Event(v1.ObjectReference{Kind:“ClusterRoleBinding”, Namespace:"", Name:“system:coredns”, UID:“70cf2177-16c5-4f17-92c1-c6262a6ca246”, APIVersion:“rbac.authorization.k8s.io/v1”, ResourceVersion:“245”, FieldPath:""}): type: ‘Normal’ reason: ‘Synced’ ClusterRoleBinding synced successfully

      I0506 06:54:02.166775       1 event.go:282] Event(v1.ObjectReference{Kind:“ClusterRoleBinding”, Namespace:"", Name:“system:controller:route-controller”, UID:“8bcc1b00-8fc2-451b-94bd-de97384f0b85”, APIVersion:“rbac.authorization.k8s.io/v1”, ResourceVersion:“184”, FieldPath:""}): type: ‘Normal’ reason: ‘Synced’ ClusterRoleBinding synced successfully

      I0506 06:54:02.166788       1 event.go:282] Event(v1.ObjectReference{Kind:“ClusterRoleBinding”, Namespace:"", Name:“kubesphere-prometheus-operator”, UID:“93455e72-98eb-4505-84de-6dc0b3b3b7b4”, APIVersion:“rbac.authorization.k8s.io/v1”, ResourceVersion:“1247”, FieldPath:""}): type: ‘Normal’ reason: ‘Synced’ ClusterRoleBinding synced successfully

      I0506 06:54:02.166801       1 event.go:282] Event(v1.ObjectReference{Kind:“ClusterRoleBinding”, Namespace:"", Name:“notification-manager-tenant-sidecar-rolebinding”, UID:“21b82320-b9d7-4248-b4c3-b57330bb6a53”, APIVersion:“rbac.authorization.k8s.io/v1”, ResourceVersion:“1511”, FieldPath:""}): type: ‘Normal’ reason: ‘Synced’ ClusterRoleBinding synced successfully

      I0506 06:54:02.166824       1 event.go:282] Event(v1.ObjectReference{Kind:“ClusterRoleBinding”, Namespace:"", Name:“system:volume-scheduler”, UID:“1f7ca883-49b1-48fa-b1d0-b08cee3f77cc”, APIVersion:“rbac.authorization.k8s.io/v1”, ResourceVersion:“160”, FieldPath:""}): type: ‘Normal’ reason: ‘Synced’ ClusterRoleBinding synced successfully

      I0506 06:54:02.180992       1 globalrolebinding_controller.go:205] Successfully synced key:admin

      I0506 06:54:02.181088       1 event.go:282] Event(v1.ObjectReference{Kind:“GlobalRoleBinding”, Namespace:"", Name:“admin”, UID:“81891542-6feb-4600-bfc2-8c60d09870f0”, APIVersion:“iam.kubesphere.io/v1alpha2”, ResourceVersion:“995”, FieldPath:""}): type: ‘Normal’ reason: ‘Synced’ GlobalRoleBinding synced successfully

      I0506 06:54:02.193942       1 clusterrolebinding_controller.go:190] Successfully synced key:admin-cluster-admin

      I0506 06:54:02.195029       1 event.go:282] Event(v1.ObjectReference{Kind:“ClusterRoleBinding”, Namespace:"", Name:“admin-cluster-admin”, UID:“25b05aa9-b6ef-414d-954d-d671725f89d9”, APIVersion:“rbac.authorization.k8s.io/v1”, ResourceVersion:“1792”, FieldPath:""}): type: ‘Normal’ reason: ‘Synced’ ClusterRoleBinding synced successfully

      看着也是正常呢,方便加个联系方式吗

        sicheng43 ks-console和ks-apiserver的日志也看看,另外你登录页面有报错提示么