kubesphere-system ks-console-b4df86d6f-tqg6p 1/1 Running 0 51m
kubesphere-system ks-controller-manager-78c4c48c75-5lxmw 0/1 CrashLoopBackOff 12 49m
kubesphere-system ks-installer-7cb866bd-4t9tw 1/1 Running 0 57m
kubesphere-system openldap-0 1/1 Running 0 51m
kubesphere-system redis-644bc597b9-pqk6p 1/1 Running 0 51m
[root@iZ2zedielqp0scsxwl1d74Z net.d]# kubectl logs ks-controller-manager-78c4c48c75-5lxmw -n kubesphere-system
W0924 11:29:50.967722 1 client_config.go:543] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
E0924 11:30:30.971151 1 server.go:81] failed to connect to ldap service, please check ldap status, error: factory is not able to fill the pool: LDAP Result Code 200 “Network Error”: dial tcp: lookup openldap.kubesphere-system.svc on 169.254.25.10:53: read udp 10.233.69.21:44000->169.254.25.10:53: i/o timeout
阿里云 单机 安装 k8s 和 kubesphere3.0 还剩点问题
[root@iZ2zedielqp0scsxwl1d74Z ]# docker ps -a | grep controll
7f8cfa514e86 85bd13080839 “controller-manager …” 4 minutes ago Exited (1) 3 minutes ago k8s_ks-controller-manager_ks-controller-manager-85c5f78799-t2tvh_kubesphere-system_4308a5ff-7b9b-4fa0-be80-ae068a88ff20_7
28af1a5957d1 kubesphere/pause:3.2 “/pause” 19 minutes ago Up 19 minutes k8s_POD_ks-controller-manager-85c5f78799-t2tvh_kubesphere-system_4308a5ff-7b9b-4fa0-be80-ae068a88ff20_0
df42330b3cc8 csiplugin/snapshot-controller “/snapshot-controlle…” 3 hours ago Up 3 hours k8s_snapshot-controller_snapshot-controller-0_kube-system_4c7893a9-3bbd-434c-9e08-7f33c11a874e_0
92116f0b20d4 kubesphere/pause:3.2 “/pause” 3 hours ago Up 3 hours k8s_POD_snapshot-controller-0_kube-system_4c7893a9-3bbd-434c-9e08-7f33c11a874e_0
c8db9ac5da04 8ed9dbffe350 “/usr/bin/kube-contr…” 3 hours ago Up 3 hours k8s_calico-kube-controllers_calico-kube-controllers-578894d4cd-9ppgq_kube-system_c5018e62-e53a-46b7-a049-28d89e2791a3_0
b15a2db6d12a kubesphere/pause:3.2 “/pause” 3 hours ago Up 3 hours k8s_POD_calico-kube-controllers-578894d4cd-9ppgq_kube-system_c5018e62-e53a-46b7-a049-28d89e2791a3_0
6abd3c039d62 ffce5e64d915 “kube-controller-man…” 6 hours ago Up 6 hours k8s_kube-controller-manager_kube-controller-manager-iz2zedielqp0scsxwl1d74z_kube-system_c114c9491ca019816d8f5ed82b8e9a2b_0
3ec562d8763b kubesphere/pause:3.2 “/pause” 6 hours ago Up 6 hours k8s_POD_kube-controller-manager-iz2zedielqp0scsxwl1d74z_kube-system_c114c9491ca019816d8f5ed82b8e9a2b_0
[root@iZ2zedielqp0scsxwl1d74Z ]# docker logs 7f8cfa514e86
W0924 14:01:12.004853 1 client_config.go:543] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
E0924 14:01:52.009471 1 server.go:81] failed to connect to ldap service, please check ldap status, error: factory is not able to fill the pool: LDAP Result Code 200 “Network Error”: dial tcp: lookup openldap.kubesphere-system.svc on 169.254.25.10:53: read udp 10.233.69.25:40553->169.254.25.10:53: i/o timeout
[root@iZ2zedielqp0scsxwl1d74Z ]#
[root@iZ2zedielqp0scsxwl1d74Z ]# getenforce
Disabled
[root@iZ2zedielqp0scsxwl1d74Z ]# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:firewalld(1)
[root@iZ2zedielqp0scsxwl1d74Z ]# docker ps -a | grep api
bdc800298266 d9fac59cfb8c “ks-apiserver –logt…” 3 minutes ago Exited (1) 3 minutes ago k8s_ks-apiserver_ks-apiserver-67b5758b8f-cn9qz_kubesphere-system_4d489ce5-db29-4175-9595-ecb529e72377_33
63a1c2c1167d kubesphere/pause:3.2 “/pause” 3 hours ago Up 3 hours k8s_POD_ks-apiserver-67b5758b8f-cn9qz_kubesphere-system_4d489ce5-db29-4175-9595-ecb529e72377_0
d81dc71d5705 56acd67ea15a “kube-apiserver –ad…” 6 hours ago Up 6 hours k8s_kube-apiserver_kube-apiserver-iz2zedielqp0scsxwl1d74z_kube-system_e0a1f0718c59c5151c8a65a2383218a0_0
60baf16201e8 kubesphere/pause:3.2 “/pause” 6 hours ago Up 6 hours k8s_POD_kube
apiserver-iz2zedielqp0scsxwl1d74z_kube-system_e0a1f0718c59c5151c8a65a2383218a0_0
[root@iZ2zedielqp0scsxwl1d74Z ]# docker logs bdc800298266
W0924 14:21:22.994847 1 client_config.go:543] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
Error: failed to connect to redis service, please check redis status, error: dial tcp: i/o timeout
2020/09/24 14:21:27 failed to connect to redis service, please check redis status, error: dial tcp: i/o timeout
[root@iZ2zedielqp0scsxwl1d74Z ]#
现在 剩下的 问题是redis 和 LDAP 不能 访问， 应该不是存储的 问题吧
bmingithubK零S
tscswcn 看下pvc有没有pending的
kubectl get pvc -A
NAMESPACE NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
kubesphere-monitoring-system prometheus-k8s-db-prometheus-k8s-0 Pending local 3h46m
kubesphere-system openldap-pvc-openldap-0 Bound pvc-c7b09ede-e3ca-4b6f-8690-cf5cd1feff32 2Gi RWO local 3h48m
kubesphere-system redis-pvc Bound pvc-5ab38411-adce-403f-831a-352228b9914b 2Gi RWO local 3h48m 我看 pvc 是 Bound
还有什么诊断 思路？
- bmingithubK零S
redis 和openladp的pod 都正常么？ 不正常的话，describe 看看。
现在
kubectl exec -it ks-controller-manager-85c5f78799-bm9l5 -n kubesphere-system sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl kubectl exec [POD] – [COMMAND] instead.
/ # cat /etc/resolv.conf
nameserver 169.254.25.10
search kubesphere-system.svc.cluster.local svc.cluster.local cluster.local
options ndots:5
/ # command terminated with exit code 137
[root@iZ2zedielqp0scsxwl1d74Z etc]# kubectl exec -it ks-controller-manager-85c5f78799-bm9l5 -n kubesphere-system sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl kubectl exec [POD] – [COMMAND] instead.
error: unable to upgrade connection: container not found (“ks-controller-manager”)
[root@iZ2zedielqp0scsxwl1d74Z etc]# kubectl exec -it ks-controller-manager-85c5f78799-bm9l5 -n kubesphere-system sh
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl kubectl exec [POD] – [COMMAND] instead.
/ # ping 169.254.25.10
PING 169.254.25.10 (169.254.25.10): 56 data bytes
好像 不行