创建部署问题时，请参考下面模板，你提供的信息越多，越容易及时获得解答。
你只花一分钟创建的问题，不能指望别人花上半个小时给你解答。
发帖前请点击 发表主题 右边的 预览(👀) 按钮，确保帖子格式正确。
操作系统信息
虚拟机 centos7 16c16G
Kubernetes版本信息
3主3work
容器运行时
docker
KubeSphere版本信息
例如：v2.1.1/v3.0.0。离线安装还是在线安装。已有K8s安装还是全套安装。
问题是什么
按Kubekey部署后kube-system中各pod反复重启
pod/calico-kube-controllers
kubectl -n kube-system logs -p pod/calico-kube-controllers-69cfcfdf6c-q4jbt | grep error
2023-02-08 12:18:27.923 [ERROR][1] client.go 272: Error getting cluster information config ClusterInformation=“default” error=Get “https://10.233.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default”: dial tcp 10.233.0.1:443: connect: connection refused
2023-02-08 12:18:27.923 [FATAL][1] main.go 124: Failed to initialize Calico datastore error=Get “https://10.233.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default”: dial tcp 10.233.0.1:443: connect: connection refused
pod/calico-node-r7ml7
Defaulted container “calico-node” out of: calico-node, upgrade-ipam (init), install-cni (init)
2023-02-08 08:23:27.341 [ERROR][9] startup/startup.go 158: failed to query kubeadm’s config map error=Get “https://10.233.0.1:443/api/v1/namespaces/kube-system/configmaps/kubeadm-config?timeout=2s”: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
pod/kube-apiserver-k8s-01
{“level”:“warn”,“ts”:“2023-02-08T08:38:22.506Z”,“logger”:“etcd-client”,“caller”:“v3/retry_interceptor.go:62”,“msg”:“retrying of unary invoker failed”,“target”:“etcd-endpoints://0xc005540c40/#initially=[https://192.168.8.81:2379;https://192.168.8.82:2379;https://192.168.8.83:2379]”,“attempt”:0,“error”:“rpc error: code = DeadlineExceeded desc = context deadline exceeded”}
{“level”:“warn”,“ts”:“2023-02-08T08:38:31.506Z”,“logger”:“etcd-client”,“caller”:“v3/retry_interceptor.go:62”,“msg”:“retrying of unary invoker failed”,“target”:“etcd-endpoints://0xc0013281c0/#initially=[https://192.168.8.81:2379;https://192.168.8.82:2379;https://192.168.8.83:2379]”,“attempt”:0,“error”:“rpc error: code = Canceled desc = context canceled”}
E0208 08:38:31.506626 1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:“context canceled”}: context canceled
E0208 08:38:31.507778 1 status.go:71] apiserver received an error that is not an metav1.Status: &errors.errorString{s:“http: Handler timeout”}: http: Handler timeout
{“level”:“warn”,“ts”:“2023-02-08T08:38:44.642Z”,“logger”:“etcd-client”,“caller”:“v3/retry_interceptor.go:62”,“msg”:“retrying of unary invoker failed”,“target”:“etcd-endpoints://0xc005540c40/#initially=[https://192.168.8.81:2379;https://192.168.8.82:2379;https://192.168.8.83:2379]”,“attempt”:0,“error”:“rpc error: code = DeadlineExceeded desc = context deadline exceeded”}
{“level”:“warn”,“ts”:“2023-02-08T08:38:46.648Z”,“logger”:“etcd-client”,“caller”:“v3/retry_interceptor.go:62”,“msg”:“retrying of unary invoker failed”,“target”:“etcd-endpoints://0xc005540c40/#initially=[https://192.168.8.81:2379;https://192.168.8.82:2379;https://192.168.8.83:2379]”,“attempt”:0,“error”:“rpc error: code = Unknown desc = context deadline exceeded”}
pod/kube-controller-manager-k8s-01
E0208 17:28:05.532707 1 leaderelection.go:330] error retrieving resource lock kube-system/kube-controller-manager: Get “https://192.168.8.81:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-controller-manager?timeout=5s”: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
E0208 17:28:40.014154 1 leaderelection.go:330] error retrieving resource lock kube-system/kube-controller-manager: the server was unable to return a response in the time allotted, but may still be processing the request (get leases.coordination.k8s.io kube-controller-manager)
pod/kube-scheduler-k8s-02
E0208 12:18:26.693794 1 leaderelection.go:330] error retrieving resource lock kube-system/kube-scheduler: Get “https://192.168.8.82:6443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/kube-scheduler?timeout=5s”: dial tcp 192.168.8.82:6443: connect: connection refused
