NAMESPACE                      NAME                                              READY   STATUS             RESTARTS   AGE     IP              NODE           NOMINATED NODE   READINESS GATES
default                        nginx-deployment-55797bd4cb-jtxr7                 0/1     CrashLoopBackOff   146        7d1h    10.244.2.23     k8s-node02     <none>           <none>
kube-system                    coredns-5c98db65d4-c6htl                          1/1     Running            8          20d     10.244.0.21     k8s-master01   <none>           <none>
kube-system                    coredns-5c98db65d4-mntt2                          1/1     Running            8          20d     10.244.0.23     k8s-master01   <none>           <none>
kube-system                    etcd-k8s-master01                                 1/1     Running            6          20d     192.168.66.10   k8s-master01   <none>           <none>
kube-system                    kube-apiserver-k8s-master01                       1/1     Running            6          20d     192.168.66.10   k8s-master01   <none>           <none>
kube-system                    kube-controller-manager-k8s-master01              1/1     Running            6          20d     192.168.66.10   k8s-master01   <none>           <none>
kube-system                    kube-flannel-ds-4vlv8                             1/1     Running            9          20d     192.168.66.20   k8s-node01     <none>           <none>
kube-system                    kube-flannel-ds-db82q                             1/1     Running            8          20d     192.168.66.21   k8s-node02     <none>           <none>
kube-system                    kube-flannel-ds-td7rv                             1/1     Running            8          20d     192.168.66.10   k8s-master01   <none>           <none>
kube-system                    kube-proxy-2r2g2                                  1/1     Running            7          20d     192.168.66.10   k8s-master01   <none>           <none>
kube-system                    kube-proxy-c6g9q                                  1/1     Running            7          20d     192.168.66.21   k8s-node02     <none>           <none>
kube-system                    kube-proxy-q7h4r                                  1/1     Running            8          20d     192.168.66.20   k8s-node01     <none>           <none>
kube-system                    kube-scheduler-k8s-master01                       1/1     Running            6          20d     192.168.66.10   k8s-master01   <none>           <none>
kubesphere-controls-system     default-http-backend-6555ff6898-rf8dp             1/1     Running            1          6d20h   10.244.1.30     k8s-node01     <none>           <none>
kubesphere-monitoring-system   alertmanager-main-0                               2/2     Running            2          6d20h   10.244.2.21     k8s-node02     <none>           <none>
kubesphere-monitoring-system   alertmanager-main-1                               2/2     Running            2          6d20h   10.244.1.34     k8s-node01     <none>           <none>
kubesphere-monitoring-system   alertmanager-main-2                               2/2     Running            2          6d20h   10.244.1.31     k8s-node01     <none>           <none>
kubesphere-monitoring-system   kube-state-metrics-56cb89fd8d-d9lcr               3/3     Running            3          6d20h   10.244.1.39     k8s-node01     <none>           <none>
kubesphere-monitoring-system   node-exporter-25p6k                               2/2     Running            2          6d20h   192.168.66.10   k8s-master01   <none>           <none>
kubesphere-monitoring-system   node-exporter-2ztz7                               2/2     Running            2          6d20h   192.168.66.20   k8s-node01     <none>           <none>
kubesphere-monitoring-system   node-exporter-xld7j                               2/2     Running            2          6d20h   192.168.66.21   k8s-node02     <none>           <none>
kubesphere-monitoring-system   notification-manager-deployment-b8fcb5676-ffgtt   1/1     Running            1          6d20h   10.244.1.38     k8s-node01     <none>           <none>
kubesphere-monitoring-system   notification-manager-deployment-b8fcb5676-ftdzw   1/1     Running            1          6d20h   10.244.2.20     k8s-node02     <none>           <none>
kubesphere-monitoring-system   notification-manager-operator-5df57c5b9d-thf67    2/2     Running            2          6d20h   10.244.1.33     k8s-node01     <none>           <none>
kubesphere-monitoring-system   prometheus-k8s-0                                  3/3     Running            4          6d20h   10.244.1.32     k8s-node01     <none>           <none>
kubesphere-monitoring-system   prometheus-k8s-1                                  3/3     Running            4          6d20h   10.244.2.22     k8s-node02     <none>           <none>
kubesphere-monitoring-system   prometheus-operator-7785b55fdf-8xrs6              2/2     Running            2          6d20h   10.244.2.26     k8s-node02     <none>           <none>
kubesphere-system              ks-apiserver-74449c98f5-n95xw                     0/1     CrashLoopBackOff   18         70m     10.244.0.26     k8s-master01   <none>           <none>
kubesphere-system              ks-console-5659dd48b7-zb4dx                       1/1     Running            1          6d20h   10.244.0.20     k8s-master01   <none>           <none>
kubesphere-system              ks-controller-manager-5698c69cf9-w298l            0/1     CrashLoopBackOff   18         70m     10.244.0.27     k8s-master01   <none>           <none>
kubesphere-system              ks-installer-78c8b69b9d-q6s2t                     1/1     Running            3          7d      10.244.2.19     k8s-node02     <none>           <none>
kubesphere-system              openldap-0                                        0/1     Pending            0          6d20h   <none>          <none>         <none>           <none>
kubesphere-system              redis-5d4844b947-79kxj                            0/1     Pending            0          6d20h   <none>          <none>         <none>           <none>
openebs                        maya-apiserver-77d8f94b58-9swqh                   1/1     Running            32         6d23h   10.244.1.35     k8s-node01     <none>           <none>
openebs                        openebs-admission-server-77b88865d4-btqfl         1/1     Running            3          6d23h   10.244.2.24     k8s-node02     <none>           <none>
openebs                        openebs-localpv-provisioner-6994dd88b8-hbt4x      1/1     Running            5          6d23h   10.244.1.40     k8s-node01     <none>           <none>
openebs                        openebs-ndm-f8dcw                                 1/1     Running            2          6d23h   192.168.66.21   k8s-node02     <none>           <none>
openebs                        openebs-ndm-operator-c69cd6666-rlxc5              1/1     Running            4          6d23h   10.244.1.37     k8s-node01     <none>           <none>
openebs                        openebs-ndm-wjgh4                                 1/1     Running            5          6d23h   192.168.66.20   k8s-node01     <none>           <none>
openebs                        openebs-ndm-z9xnn                                 1/1     Running            2          6d23h   192.168.66.10   k8s-master01   <none>           <none>
openebs                        openebs-provisioner-7b87d7956-kzwpv               1/1     Running            4          6d23h   10.244.1.36     k8s-node01     <none>           <none>
openebs                        openebs-snapshot-operator-6959d684cf-m2wjl        2/2     Running            5          6d23h   10.244.2.25     k8s-node02     <none>           <none>
 kubectl log ks-apiserver-74449c98f5-n95xw --namespace kubesphere-system
log is DEPRECATED and will be removed in a future version. Use logs instead.
W0124 15:26:06.422514       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 10.102.63.112:6379: connect: connection refused
2021/01/24 15:26:06 failed to connect to redis service, please check redis status, error: dial tcp 10.102.63.112:6379: connect: connection refused
[root@k8s-master01 ~]# kubectl log ks-controller-manager-5698c69cf9-w298l --namespace kubesphere-system
log is DEPRECATED and will be removed in a future version. Use logs instead.
W0124 15:25:34.430789       1 client_config.go:543] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
E0124 15:25:34.482325       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 10.96.0.10:53: no such host

    antsgod

    kubesphere-system openldap-0 0/1 Pending 0 6d20h <none> <none> <none> <none>
    kubesphere-system redis-5d4844b947-79kxj 0/1 Pending 0

    pod 一直 pending 应该是存储没有正确配置