环境CentOS8，docker 20.10.4 ce
使用安装命令：
./kk create cluster --with-kubernetes v1.18.6 --with-kubesphere v3.0.0
检查k8s版本确为1.18.6
pods:
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system calico-kube-controllers-578894d4cd-7sxln 1/1 Running 0 41m
kube-system calico-node-6dmng 1/1 Running 0 41m
kube-system coredns-6b55b6764d-9mxnm 1/1 Running 0 41m
kube-system coredns-6b55b6764d-9zkxf 1/1 Running 0 41m
kube-system kube-apiserver-kubernetes.master 1/1 Running 0 41m
kube-system kube-controller-manager-kubernetes.master 1/1 Running 0 41m
kube-system kube-proxy-wvsk7 1/1 Running 0 41m
kube-system kube-scheduler-kubernetes.master 1/1 Running 0 41m
kube-system metrics-server-f47758d8f-slpq4 1/1 Running 0 40m
kube-system nodelocaldns-frjzs 1/1 Running 0 41m
kube-system openebs-localpv-provisioner-84446d4bd7-gzn64 1/1 Running 0 41m
kube-system openebs-ndm-mz597 1/1 Running 0 41m
kube-system openebs-ndm-operator-6456dc9db-kmdt6 1/1 Running 1 41m
kube-system snapshot-controller-0 1/1 Running 0 39m
kubesphere-controls-system default-http-backend-857d7b6856-975cl 1/1 Running 0 38m
kubesphere-monitoring-system alertmanager-main-0 2/2 Running 0 37m
kubesphere-monitoring-system kube-state-metrics-95c974544-wd884 3/3 Running 0 37m
kubesphere-monitoring-system node-exporter-lcbj5 2/2 Running 0 37m
kubesphere-monitoring-system notification-manager-deployment-7c8df68d94-brkgr 1/1 Running 0 37m
kubesphere-monitoring-system notification-manager-operator-6958786cd6-ksncg 2/2 Running 0 37m
kubesphere-monitoring-system prometheus-k8s-0 3/3 Running 1 37m
kubesphere-monitoring-system prometheus-operator-84d58bf775-bjt9r 2/2 Running 0 37m
kubesphere-system ks-apiserver-7c9464dfbb-ljtkt 1/1 Running 0 37m
kubesphere-system ks-console-b4df86d6f-d8gzh 1/1 Running 0 38m
kubesphere-system ks-controller-manager-85ff4bb57c-lwv2m 0/1 CrashLoopBackOff 10 37m
kubesphere-system ks-installer-7cb866bd-lbzv9 1/1 Running 0 41m
kubesphere-system openldap-0 1/1 Running 0 39m
kubesphere-system redis-644bc597b9-krrn8 1/1 Running 0 39m
查看ks-controller-manager-85ff4bb57c-lwv2m的日志：
W0303 21:49:03.403879 1 client_config.go:543] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
E0303 21:50:03.405020 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 10.233.119.11:389: i/o timeout
openldap-0的日志就是大量的
60404bae conn=1330 fd=12 ACCEPT from IP=192.168.1.8:60530 (IP=0.0.0.0:389)
60404bae conn=1330 fd=12 closed (connection lost)
60404bb7 conn=1331 fd=12 ACCEPT from IP=192.168.1.8:60642 (IP=0.0.0.0:389)
60404bb7 conn=1331 fd=12 closed (connection lost)
请教一下，这个问题如何进一步查找及解决？
