创建部署问题时，请参考下面模板，你提供的信息越多，越容易及时获得解答。如果未按模板创建问题，管理员有权关闭问题。
确保帖子格式清晰易读，用 markdown code block 语法格式化代码块。
你只花一分钟创建的问题，不能指望别人花上半个小时给你解答。
操作系统信息
虚拟机，Centos7
Kubernetes版本信息
Client Version: version.Info{Major:“1”, Minor:“21”, GitVersion:“v1.21.5”, GitCommit:“aea7bbadd2fc0cd689de94a54e5b7b758869d691”, GitTreeState:“clean”, BuildDate:“2021-09-15T21:10:45Z”, GoVersion:“go1.16.8”, Compiler:“gc”, Platform:“linux/amd64”}
Server Version: version.Info{Major:“1”, Minor:“21”, GitVersion:“v1.21.5”, GitCommit:“aea7bbadd2fc0cd689de94a54e5b7b758869d691”, GitTreeState:“clean”, BuildDate:“2021-09-15T21:04:16Z”, GoVersion:“go1.16.8”, Compiler:“gc”, Platform:“linux/amd64”}
容器运行时
将 docker version / crictl version / nerdctl version 结果贴在下方
KubeSphere版本信息
v3.1.0升级到v3.2.1
问题是什么
TASK [check-result : KubeSphere | Waiting for ks-apiserver] ********************
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (30 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (29 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (28 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (27 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (26 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (25 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (24 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (23 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (22 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (21 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (20 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (19 retries left).
ks-apiserver 没问题
kubesphere-system ks-apiserver-5f8b97c9d5-82srj 1/1 Running 0 69m
kubesphere-system ks-apiserver-5f8b97c9d5-cgzwq 1/1 Running 0 69m
kubesphere-system ks-apiserver-5f8b97c9d5-rwlrp 1/1 Running 0 69m
[root@master1 ~]# kubectl -n kubesphere-system logs ks-apiserver-5f8b97c9d5-82srj
W0128 14:41:07.914142 1 client_config.go:615] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
W0128 14:41:07.918383 1 client_config.go:615] Neither –kubeconfig nor –master was specified. Using the inClusterConfig. This might not work.
I0128 14:41:08.544145 1 interface.go:60] start helm repo informer
I0128 14:41:08.616016 1 apiserver.go:356] Start cache objects
I0128 14:41:10.185385 1 apiserver.go:562] Finished caching objects
I0128 14:41:10.185422 1 apiserver.go:278] Start listening on :9090
W0128 15:19:32.905104 1 jwt.go:53] EOF
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (18 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (17 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (16 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (15 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (14 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (13 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (12 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (11 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (10 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (9 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (8 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (7 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (6 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (5 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (4 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (3 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (2 retries left).
FAILED - RETRYING: KubeSphere | Waiting for ks-apiserver (1 retries left).
fatal: [localhost]: FAILED! => {“attempts”: 30, “changed”: true, “cmd”: “/usr/local/bin/kubectl get pod -n kubesphere-system -o wide | grep ks-apiserver | awk ‘{print $3}’”, “delta”: “0:00:00.129395”, “end”: “2022-01-27 18:56:02.388825”, “rc”: 0, “start”: “2022-01-27 18:56:02.259430”, “stderr”: "", “stderr_lines”: [], “stdout”: “CrashLoopBackOff\nCrashLoopBackOff\nCrashLoopBackOff”, “stdout_lines”: [“CrashLoopBackOff”, “CrashLoopBackOff”, “CrashLoopBackOff”]}
PLAY RECAP *********************************************************************
localhost : ok=20 changed=13 unreachable=0 failed=1 skipped=15 rescued=0 ignored=0
