创建部署问题时，请参考下面模板，你提供的信息越多，越容易及时获得解答。如果未按模板创建问题，管理员有权关闭问题。
确保帖子格式清晰易读，用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题，不能指望别人花上半个小时给你解答。
操作系统信息
五台云服务器，三台为腾讯云，一台天翼云，一台阿里云
系统全都是Centos7.6，
两台为2C/2G，一台为2C/4G(master)，一台4C8G，一台4C16G
Kubernetes版本信息
将 kubectl version 命令执行结果贴在下方
[root@k8smaster ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:07:13Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
容器运行时
docker version
[root@k8smaster ~]# docker version
Client: Docker Engine - Community
Version: 19.03.6
API version: 1.40
Go version: go1.12.16
Git commit: 369ce74a3c
Built: Thu Feb 13 01:29:29 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.6
API version: 1.40 (minimum version 1.12)
Go version: go1.12.16
Git commit: 369ce74a3c
Built: Thu Feb 13 01:28:07 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683
crictl version
[root@k8smaster ~]# crictl version
WARN[0000] runtime connect using default endpoints: [unix:///var/run/dockershim.sock unix:///run/containerd/containerd.sock unix:///run/crio/crio.sock unix:///var/run/cri-dockerd.sock]. As the default settings are now deprecated, you should set the endpoint instead.
Version: 0.1.0
RuntimeName: docker
RuntimeVersion: 19.03.6
RuntimeApiVersion: 1.40.0
KubeSphere版本信息
v2.1.1
在线安装
在已有K8s上安装
问题是什么
在已有k8s集群上执行最小化安装，安装完成后进入dashboard，发现只能查看到一个节点的cpu，内存和存储信息，但是每个节点的容器组信息都正常显示。
在这之后又安装了一些组件，包括metrics-server、devops、alerting
但是安装完成后还是同样所有的pod状态都显示正常，在工作台中还是只能看到一个节点的监控信息
[root@k8smaster ~]# kubectl get pods --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
ingress-nginx nginx-ingress-controller-5csxz 1/1 Running 0 13h 115.239.212.124 k8snode3 <none> <none>
ingress-nginx nginx-ingress-controller-b6zxp 1/1 Running 0 13h 49.232.185.131 k8smaster <none> <none>
ingress-nginx nginx-ingress-controller-dhw44 1/1 Running 0 13h 47.101.35.234 k8snode4 <none> <none>
ingress-nginx nginx-ingress-controller-gnjbp 1/1 Running 0 13h 120.53.100.56 k8snode2 <none> <none>
ingress-nginx nginx-ingress-controller-sdk55 1/1 Running 0 13h 101.42.161.179 k8snode1 <none> <none>
kube-system coredns-7f9c544f75-929l4 1/1 Running 0 14h 10.244.0.3 k8smaster <none> <none>
kube-system coredns-7f9c544f75-fr7c9 1/1 Running 0 14h 10.244.0.2 k8smaster <none> <none>
kube-system etcd-k8smaster 1/1 Running 0 14h 49.232.185.131 k8smaster <none> <none>
kube-system kube-apiserver-k8smaster 1/1 Running 0 13h 49.232.185.131 k8smaster <none> <none>
kube-system kube-controller-manager-k8smaster 1/1 Running 1 14h 49.232.185.131 k8smaster <none> <none>
kube-system kube-flannel-ds-amd64-2ffwq 1/1 Running 0 13h 49.232.185.131 k8smaster <none> <none>
kube-system kube-flannel-ds-amd64-d6x5k 1/1 Running 0 13h 101.42.161.179 k8snode1 <none> <none>
kube-system kube-flannel-ds-amd64-m9shq 1/1 Running 1 13h 120.53.100.56 k8snode2 <none> <none>
kube-system kube-flannel-ds-amd64-p7cvw 1/1 Running 1 13h 47.101.35.234 k8snode4 <none> <none>
kube-system kube-flannel-ds-amd64-tx7wp 1/1 Running 0 13h 115.239.212.124 k8snode3 <none> <none>
kube-system kube-proxy-2ktgc 1/1 Running 0 13h 101.42.161.179 k8snode1 <none> <none>
kube-system kube-proxy-j2gnj 1/1 Running 0 13h 120.53.100.56 k8snode2 <none> <none>
kube-system kube-proxy-nttzp 1/1 Running 0 14h 49.232.185.131 k8smaster <none> <none>
kube-system kube-proxy-snhsn 1/1 Running 0 13h 47.101.35.234 k8snode4 <none> <none>
kube-system kube-proxy-z47vb 1/1 Running 0 13h 115.239.212.124 k8snode3 <none> <none>
kube-system kube-scheduler-k8smaster 1/1 Running 1 14h 49.232.185.131 k8smaster <none> <none>
kube-system metrics-server-66444bf745-p4nrq 1/1 Running 0 12h 10.244.4.10 k8snode4 <none> <none>
kube-system tiller-deploy-547d695f46-v6nj4 1/1 Running 0 13h 10.244.3.3 k8snode3 <none> <none>
kubesphere-alerting-system alerting-client-685d4d47fc-7h7hp 1/1 Running 3 12h 10.244.4.20 k8snode4 <none> <none>
kubesphere-alerting-system alerting-db-ctrl-job-bt272 0/1 Completed 0 12h 10.244.4.16 k8snode4 <none> <none>
kubesphere-alerting-system alerting-db-init-job-dl74w 0/1 Completed 0 12h 10.244.4.15 k8snode4 <none> <none>
kubesphere-alerting-system alerting-executor-94b9899f9-z8z7w 2/2 Running 0 12h 10.244.3.18 k8snode3 <none> <none>
kubesphere-alerting-system alerting-manager-58cd9ddcc6-d26nc 1/1 Running 0 12h 10.244.4.19 k8snode4 <none> <none>
kubesphere-alerting-system alerting-watcher-55b7594bbc-l4j5n 1/1 Running 0 12h 10.244.4.17 k8snode4 <none> <none>
kubesphere-alerting-system notification-db-ctrl-job-vh5t4 0/1 Completed 0 12h 10.244.3.19 k8snode3 <none> <none>
kubesphere-alerting-system notification-db-init-job-g95s7 0/1 Completed 0 12h 10.244.3.17 k8snode3 <none> <none>
kubesphere-alerting-system notification-deployment-68d5b6c8ff-8fnj5 1/1 Running 3 12h 10.244.4.18 k8snode4 <none> <none>
kubesphere-controls-system default-http-backend-5d464dd566-gl9w2 1/1 Running 0 13h 10.244.3.7 k8snode3 <none> <none>
kubesphere-controls-system kubectl-admin-6c664db975-c9qgm 1/1 Running 0 13h 10.244.3.11 k8snode3 <none> <none>
kubesphere-devops-system ks-devops-db-ctrl-job-6tghw 0/1 Completed 1 12h 10.244.4.24 k8snode4 <none> <none>
kubesphere-devops-system ks-devops-db-init-job-kb6px 0/1 Completed 0 12h 10.244.3.21 k8snode3 <none> <none>
kubesphere-devops-system ks-jenkins-65bd6cc59c-bkgvp 1/1 Running 0 12h 10.244.4.26 k8snode4 <none> <none>
kubesphere-devops-system ks-sonarqube-postgresql-666d5bd77-6bdsk 1/1 Running 0 12h 10.244.4.23 k8snode4 <none> <none>
kubesphere-devops-system ks-sonarqube-sonarqube-f68dd5ff5-2g87v 1/1 Running 0 12h 10.244.4.21 k8snode4 <none> <none>
kubesphere-devops-system s2ioperator-0 1/1 Running 1 12h 10.244.3.22 k8snode3 <none> <none>
kubesphere-devops-system uc-jenkins-update-center-b465bf4d-tqdkj 1/1 Running 0 12h 10.244.3.16 k8snode3 <none> <none>
kubesphere-monitoring-system kube-state-metrics-566cdbcb48-8fn5x 4/4 Running 0 13h 10.244.4.7 k8snode4 <none> <none>
kubesphere-monitoring-system node-exporter-246gn 2/2 Running 0 13h 120.53.100.56 k8snode2 <none> <none>
kubesphere-monitoring-system node-exporter-hbxrj 2/2 Running 0 13h 115.239.212.124 k8snode3 <none> <none>
kubesphere-monitoring-system node-exporter-jg6n6 2/2 Running 0 13h 101.42.161.179 k8snode1 <none> <none>
kubesphere-monitoring-system node-exporter-tz8l4 2/2 Running 0 13h 49.232.185.131 k8smaster <none> <none>
kubesphere-monitoring-system node-exporter-xkshg 2/2 Running 0 13h 47.101.35.234 k8snode4 <none> <none>
kubesphere-monitoring-system prometheus-k8s-0 3/3 Running 1 13h 10.244.4.9 k8snode4 <none> <none>
kubesphere-monitoring-system prometheus-k8s-system-0 3/3 Running 1 13h 10.244.3.10 k8snode3 <none> <none>
kubesphere-monitoring-system prometheus-operator-6b97679cfd-klx9j 1/1 Running 0 13h 10.244.3.8 k8snode3 <none> <none>
kubesphere-system etcd-f988bdb6f-jrpwq 1/1 Running 0 12h 10.244.3.15 k8snode3 <none> <none>
kubesphere-system ks-account-6fb7544477-j8zh9 1/1 Running 0 12h 10.244.0.20 k8smaster <none> <none>
kubesphere-system ks-apigateway-6bd5c74bdc-w9ccg 1/1 Running 0 12h 10.244.0.19 k8smaster <none> <none>
kubesphere-system ks-apiserver-85d679c844-2gwhp 1/1 Running 0 12h 10.244.0.18 k8smaster <none> <none>
kubesphere-system ks-console-c5bb4694d-bfvcp 1/1 Running 0 12h 10.244.0.21 k8smaster <none> <none>
kubesphere-system ks-controller-manager-6f4694cb6b-hx84l 1/1 Running 0 12h 10.244.0.22 k8smaster <none> <none>
kubesphere-system ks-installer-75b8d89dff-2bz2b 1/1 Running 0 13h 10.244.4.6 k8snode4 <none> <none>
kubesphere-system minio-845b7bd867-h6pch 1/1 Running 0 12h 10.244.3.13 k8snode3 <none> <none>
kubesphere-system mysql-67cd66d5d-nrrkn 1/1 Running 0 12h 10.244.4.14 k8snode4 <none> <none>
kubesphere-system openldap-0 1/1 Running 0 13h 10.244.0.7 k8smaster <none> <none>
kubesphere-system redis-6fd6c6d6f9-5vrst 1/1 Running 0 13h 10.244.0.6 k8smaster <none> <none>
openebs openebs-admission-server-5cf6864fbf-cfdnn 1/1 Running 0 13h 10.244.3.6 k8snode3 <none> <none>
openebs openebs-apiserver-bc55cd99b-5dt7r 1/1 Running 3 13h 10.244.3.5 k8snode3 <none> <none>
openebs openebs-localpv-provisioner-85ff89dd44-kvt8q 1/1 Running 0 13h 10.244.4.3 k8snode4 <none> <none>
openebs openebs-ndm-6ml22 1/1 Running 0 13h 115.239.212.124 k8snode3 <none> <none>
openebs openebs-ndm-9vqlp 1/1 Running 0 13h 120.53.100.56 k8snode2 <none> <none>
openebs openebs-ndm-dks6t 1/1 Running 0 13h 47.101.35.234 k8snode4 <none> <none>
openebs openebs-ndm-mzm8q 1/1 Running 0 13h 101.42.161.179 k8snode1 <none> <none>
openebs openebs-ndm-nxvdb 1/1 Running 0 13h 49.232.185.131 k8smaster <none> <none>
openebs openebs-ndm-operator-87df44d9-dqjr5 1/1 Running 1 13h 10.244.4.5 k8snode4 <none> <none>
openebs openebs-provisioner-7f86c6bb64-s9xb7 1/1 Running 0 13h 10.244.4.4 k8snode4 <none> <none>
openebs openebs-snapshot-operator-54b9c886bf-pblvw 2/2 Running 0 13h 10.244.3.4 k8snode3 <none> <none>
