创建部署问题时，请参考下面模板：
操作系统信息
虚拟机，Centos7.5，4C/8G

Kubernetes版本信息
v1.20.4，多节点

KubeSphere版本信息
v3.0，全套，在线安装

问题是什么
安装过程中报错，无法启动：
INFO[10:27:00 CST] Refreshing etcd configuration
INFO[10:27:01 CST] Backup etcd data regularly
INFO[10:27:09 CST] Get cluster status
[vm11 192.168.3.101] MSG:
Cluster already exists.
[vm11 192.168.3.101] MSG:
v1.20.4
WARN[10:40:25 CST] Task failed …
WARN[10:40:25 CST] error: Failed to upload kubeadm certs: Failed to exec command: sudo -E /bin/sh -c “/usr/local/bin/kubeadm init phase upload-certs –upload-certs”
I0831 10:38:08.272540 1996 version.go:254] remote version is much newer: v1.22.1; falling back to: stable-1.20
[upload-certs] Storing the certificates in Secret “kubeadm-certs” in the “kube-system” Namespace
error execution phase upload-certs: error uploading certs: error creating token: timed out waiting for the condition
To see the stack trace of this error execute with –v=5 or higher: Process exited with status 1
Error: Failed to get cluster status: Failed to upload kubeadm certs: Failed to exec command: sudo -E /bin/sh -c “/usr/local/bin/kubeadm init phase upload-certs –upload-certs”
I0831 10:38:08.272540 1996 version.go:254] remote version is much newer: v1.22.1; falling back to: stable-1.20
[upload-certs] Storing the certificates in Secret “kubeadm-certs” in the “kube-system” Namespace
error execution phase upload-certs: error uploading certs: error creating token: timed out waiting for the condition
To see the stack trace of this error execute with –v=5 or higher: Process exited with status 1

    我是全新安装的，一开始是报安装完成，启动 timeout了。我重启虚拟机后，就报这个了。

      xiao7cn 看着感觉像之前的集群已经装好了。 你先用kk delete cluster 删除集群之后再重新安装试一下。

        现在报 port 6443 is in use. 我的haproxy是这么配置的：

        lobal
        log /dev/log local0 warning
        chroot /var/lib/haproxy
        pidfile /var/run/haproxy.pid
        maxconn 4000
        user haproxy
        group haproxy
        daemon


        stats socket /var/lib/haproxy/stats


        defaults
        log global
        option httplog
        option dontlognull
        timeout connect 5000
        timeout client 50000
        timeout server 50000


        frontend kube-apiserver
        bind *:6443
        mode tcp
        option tcplog
        default_backend kube-apiserver


        backend kube-apiserver
        mode tcp
        option tcplog
        option tcp-check
        balance roundrobin
        default-server inter 10s downinter 5s rise 2 fall 2 slowstart 60s maxconn 250 maxqueue 256 weight 100
        server kube-apiserver-1 192.168.3.101:6443 check # Replace the IP address with your own.
        server kube-apiserver-2 192.168.3.102:6443 check # Replace the IP address with your own.
        server kube-apiserver-3 192.168.3.103:6443 check # Replace the IP address with your own.

        是不是 ha proxy 的端口与 apiserver 的端口要区别开？