chrinly [root@k8s-master-01 ~]# kubectl get pod --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-5c6c9cf6c8-7r9p7 1/1 Running 0 21h kube-system coredns-5c6c9cf6c8-xqjwd 1/1 Running 0 21h kube-system kubernetes-dashboard-8f846679-9fdxh 1/1 Running 0 21h kube-system tiller-deploy-6787c946f8-vxd64 1/1 Running 0 5h1m kubesphere-controls-system default-http-backend-6555ff6898-ksb5x 1/1 Running 0 4h27m kubesphere-monitoring-system kube-state-metrics-7984bf6d6d-zx7bw 4/4 Running 0 4h20m kubesphere-monitoring-system node-exporter-6cxcf 2/2 Running 0 4h20m kubesphere-monitoring-system node-exporter-dr28f 2/2 Running 0 4h20m kubesphere-monitoring-system node-exporter-kgttf 2/2 Running 0 4h20m kubesphere-monitoring-system node-exporter-qxm8s 2/2 Running 0 4h20m kubesphere-monitoring-system prometheus-k8s-0 0/3 Pending 0 4h19m kubesphere-monitoring-system prometheus-k8s-system-0 0/3 Pending 0 4h19m kubesphere-monitoring-system prometheus-operator-545df648fb-jlzml 1/1 Running 0 4h20m kubesphere-system ks-account-7d57dc95fc-brzzj 0/1 Init:1/2 0 4h25m kubesphere-system ks-account-7d57dc95fc-bwhrx 0/1 Init:1/2 0 4h25m kubesphere-system ks-account-7d57dc95fc-r9zdp 0/1 Init:1/2 0 4h25m kubesphere-system ks-apigateway-d6f89b96f-2ds6r 0/1 CrashLoopBackOff 55 4h25m kubesphere-system ks-apigateway-d6f89b96f-qxkt6 0/1 CrashLoopBackOff 55 4h25m kubesphere-system ks-apigateway-d6f89b96f-wx9bf 0/1 CrashLoopBackOff 56 4h25m kubesphere-system ks-apiserver-5dff5c594d-ck7xk 1/1 Running 0 4h25m kubesphere-system ks-apiserver-5dff5c594d-jpn8g 1/1 Running 0 4h25m kubesphere-system ks-apiserver-5dff5c594d-xls89 1/1 Running 0 4h25m kubesphere-system ks-console-5c666c644-c25xc 1/1 Running 0 4h23m kubesphere-system ks-console-5c666c644-r8m67 1/1 Running 0 4h23m kubesphere-system ks-console-5c666c644-smmz9 1/1 Running 0 4h23m kubesphere-system ks-controller-manager-779d9c6bbf-5hlgz 1/1 Running 2 4h24m kubesphere-system ks-controller-manager-779d9c6bbf-8bw7k 1/1 Running 3 4h24m kubesphere-system ks-controller-manager-779d9c6bbf-jx92x 1/1 Running 1 4h24m kubesphere-system ks-installer-59fb465b7-l96c2 1/1 Running 0 4h39m kubesphere-system openldap-0 0/1 Pending 0 4h29m kubesphere-system redis-ha-haproxy-75776f44c4-c42dv 1/1 Running 44 4h30m kubesphere-system redis-ha-haproxy-75776f44c4-ndjg8 1/1 Running 46 4h30m kubesphere-system redis-ha-haproxy-75776f44c4-r8zt8 1/1 Running 52 4h30m kubesphere-system redis-ha-server-0 0/2 Pending 0 4h30m openebs init-pvc-2e17c54b-89b8-47df-a86d-2b884e594eb3 0/1 Completed 0 4h23m openebs init-pvc-63ef0b30-75be-4eaf-a36c-367f28702730 0/1 Completed 0 4h17m openebs init-pvc-981d9d0f-2ba0-4bc4-a535-cbf1c8717f7d 0/1 Completed 0 4h30m openebs init-pvc-a358bb04-d012-4af5-a60a-156941b1b95d 0/1 Completed 0 4h23m openebs init-pvc-ccaa6c91-7cfd-4bb8-830c-53b502bafddb 0/1 Completed 0 4h17m openebs maya-apiserver-77d8f94b58-nvslg 1/1 Running 17 21h openebs openebs-admission-server-77b88865d4-rk6fw 1/1 Running 0 21h openebs openebs-localpv-provisioner-6994dd88b8-f26qq 1/1 Running 10 21h openebs openebs-ndm-2qmtx 1/1 Running 0 21h openebs openebs-ndm-6688j 1/1 Running 0 21h openebs openebs-ndm-cl6vk 1/1 Running 0 21h openebs openebs-ndm-dp7jq 1/1 Running 0 21h openebs openebs-ndm-operator-c69cd6666-btkw5 1/1 Running 1 21h openebs openebs-provisioner-7b87d7956-kwgzv 1/1 Running 10 21h openebs openebs-snapshot-operator-6959d684cf-k9g25 2/2 Running 11 21h openebs percona-767db88d9d-rrxmx 0/1 Pending 0 4h45m [root@k8s-master-01 ~]#
rayzhou2017 pptfz 有没有因为安装失败不出声就放弃的用户我不清楚，不过确确实实安装这个部分是一个需要改进的地方，而且正在改。但是凡是遇到安装问题且跟我们联系的据我所知最后都安装成功了。你要仔细看安装文档，我们的文档是写得很谨慎的，不能漏掉东西。
rayzhou2017 pptfz 你首先要确认最小安装成功过吗？如果这个都没成功那要仔细找问题，实在不知道怎么回事写信到kubesphere@yunify.com，写明你的远程登录环境信息，让我们的人上去帮你看看到底怎么回事。
pptfz rayzhou2017 mac本pd创建的虚拟机，一个master（2c4g 64g硬盘），两个node(2c6g 32g硬盘) centos7.7，内核3.10，helm2.16.3，docker18.09.9，kubeadm安装k8s1.16.9，helm及docker都已配置阿里云加速 存储nfs，安装在了node1节点，参考文章 https://blog.csdn.net/weixin_37546425/article/details/104290906 最小化安装，kubectl apply -f https://raw.githubusercontent.com/kubesphere/ks-installer/master/kubesphere-minimal.yaml kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath=‘{.items[0].metadata.name}’) -f 刷新日志过程中有一处报错 昨天做的时候遇到过这个报错，然后我把kubectl链接到了/usr/local/bin下，但是也不行，kubeadm安装的k8s，kubectl是在/usr/bin下 登陆后报错如下 master上查看pod，有问题的pod如下
Cauchy pptfz nfs是自己搭的吗？如果是的话exportfs里建议这样配 *(rw,insecure,sync,no_subtree_check,no_root_squash)，而且要保证nfs设置成default storage class哦
chrinly rayzhou2017 [root@k8s-master-01 ~]# kubectl get pod --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE default nfs-client-provisioner-795cfb955-xdpk2 1/1 Running 0 28h demo-project coffee-svc-xjs05a-59b8b7fbd5-5ncrl 1/1 Running 0 3h26m demo-project tea-svc-s7sp65-7f7987d796-kg85s 1/1 Running 0 3h41m demo-project tomcat-z2s2fu-596c98c8d8-jpvlv 1/1 Running 0 3h17m kube-system coredns-5c6c9cf6c8-j59r7 1/1 Running 0 44h kube-system coredns-5c6c9cf6c8-trmlh 1/1 Running 0 44h kube-system heapster-778c6b467-662pd 1/1 Running 0 27h kube-system kubernetes-dashboard-8f846679-sqj2z 1/1 Running 0 44h kube-system metrics-server-65ffd78c7f-vxngg 1/1 Running 0 26h kube-system tiller-deploy-6787c946f8-gw4wk 1/1 Running 0 28h kubesphere-controls-system default-http-backend-6555ff6898-d2lh6 1/1 Running 0 28h kubesphere-controls-system kubectl-admin-74fdfc47c7-dzdkj 1/1 Running 0 27h kubesphere-controls-system kubesphere-router-demo-project-76cf544c5-dkmbc 1/1 Running 0 3h56m kubesphere-monitoring-system kube-state-metrics-7984bf6d6d-c5h5j 4/4 Running 0 27h kubesphere-monitoring-system node-exporter-cq79j 2/2 Running 0 27h kubesphere-monitoring-system node-exporter-lsx9j 2/2 Running 0 27h kubesphere-monitoring-system node-exporter-rps8b 2/2 Running 0 27h kubesphere-monitoring-system node-exporter-zvjkq 2/2 Running 0 27h kubesphere-monitoring-system prometheus-k8s-0 3/3 Running 1 27h kubesphere-monitoring-system prometheus-k8s-system-0 3/3 Running 1 27h kubesphere-monitoring-system prometheus-operator-545df648fb-9p4zd 1/1 Running 0 27h kubesphere-system etcd-b7959ccd7-9pt4g 1/1 Running 0 35m kubesphere-system ks-account-fb4599477-8hxk8 1/1 Running 0 32m kubesphere-system ks-account-fb4599477-nm489 1/1 Running 0 31m kubesphere-system ks-account-fb4599477-wz5mc 1/1 Running 0 30m kubesphere-system ks-apigateway-845bddf4f8-bl867 1/1 Running 0 32m kubesphere-system ks-apigateway-845bddf4f8-pchpw 1/1 Running 0 31m kubesphere-system ks-apigateway-845bddf4f8-sh8z2 1/1 Running 0 32m kubesphere-system ks-apiserver-cdd8f86f7-6zp2q 1/1 Running 0 31m kubesphere-system ks-apiserver-cdd8f86f7-s7qc2 1/1 Running 0 32m kubesphere-system ks-apiserver-cdd8f86f7-vvwsq 1/1 Running 0 32m kubesphere-system ks-console-565d7c4585-bt9jv 1/1 Running 0 31m kubesphere-system ks-console-565d7c4585-lsvwt 1/1 Running 0 31m kubesphere-system ks-console-565d7c4585-lw8t4 1/1 Running 0 31m kubesphere-system ks-controller-manager-75849487f9-grrqw 1/1 Running 0 31m kubesphere-system ks-controller-manager-75849487f9-j9gg8 1/1 Running 0 31m kubesphere-system ks-controller-manager-75849487f9-x9lmw 1/1 Running 0 31m kubesphere-system ks-installer-59fb465b7-4lqzv 1/1 Running 0 28h kubesphere-system minio-8cd46c8d9-hf69b 1/1 Running 0 37m kubesphere-system mysql-b5597d996-gwd8p 1/1 Running 0 35m kubesphere-system openldap-0 1/1 Running 0 28h kubesphere-system openldap-1 1/1 Running 0 28h kubesphere-system redis-ha-haproxy-75776f44c4-2qf64 1/1 Running 0 28h kubesphere-system redis-ha-haproxy-75776f44c4-blp48 1/1 Running 0 28h kubesphere-system redis-ha-haproxy-75776f44c4-wmdrq 1/1 Running 0 28h kubesphere-system redis-ha-server-0 2/2 Running 0 28h kubesphere-system redis-ha-server-1 2/2 Running 0 28h kubesphere-system redis-ha-server-2 2/2 Running 0 28h openpitrix-system hyperpitrix-release-app-job-gzhmb 0/1 Completed 0 23m openpitrix-system openpitrix-hyperpitrix-deployment-54d58c9bfc-9mhqg 1/1 Running 0 24m openpitrix-system openpitrix-rp-kubernetes-deployment-68c6cc66ff-7h8ht 1/1 Running 0 24m
