18060746374 使用命令看日志kubectl logs -f ks-installer-75b8d89dff-ks7zh -n kubesphere-system 输出github.com/flant/shell-operator/pkg/kube_events_manager/kube_events_manager.go:354: Failed to list *unstructured.Unstructured: Get https://10.96.0.1:443/api/v1/namespaces/kubesphere-system/configmaps?fieldSelector=metadata.name%3Dks-installer&limit=500&resourceVersion=0: dial tcp 10.96.0.1:443: i/o timeout
18060746374 kevendeng 查看describe出现了 Warning Unhealthy 52m kubelet, k8s-node1 Liveness probe failed: Get https://172.16.1.153:6443/healthz: dial tcp 172.16.1.153:6443: connect: no route to host 查看logs error: etcdserver: mvcc: required revision has been compacted 有点没头绪
kevendeng 18060746374 检查下kube-apiserver所在节点的资源使用情况，是否资源已经不足，导致apiserver响应太慢了。 再看看kubelet日志：journalctl -u kubelet，看看有没有其他详细错误日志。
kevendeng 18060746374 你之前的内存是多少呢？ 现在重新触发一次安装吧： kubectl rollout restart deploy ks-installer -n kubesphere-system
18060746374 kevendeng 是的，现在安装是有pod，现在出现另外一个问题 ks-account-596657f8c6-bcgf4一直是init,看了log,提示Error from server (BadRequest): container “ks-account” in pod “ks-account-596657f8c6-bcgf4” is waiting to start: PodInitializing describe： ks-apigateway-78bcdc8ffc-ss9bd 状态是： CrashLoopBackOff 日志报错，好像是redis， unable to reach redis hostdial tcp: i/o timeout describe:Ready是false
18060746374 kevendeng 第二天重新启动就好了 但是有出现安装devops一直卡着， 使用kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath=‘{.items[0].metadata.name}’) -f名称查看错误 “Error: timed out waiting for the condition”
