kubesphere3.0版本用kk给集群添加新节点的时候,默认不是利用之前已经下载到本地的相关镜像文件而是重新从拉取?
以下是我的配置文件信息:

10.16.146.15是现有主节点,想再添加一个10.16.146.13主节点
以下是我添加节点时的报错信息:
INFO[23:56:02 CST] Generating etcd certs
INFO[23:56:05 CST] Synchronizing etcd certs
INFO[23:56:06 CST] Creating etcd service
INFO[23:56:19 CST] Starting etcd cluster
[10.16.146.15 10.16.146.15] MSG:
Configuration file already exists
Waiting for etcd to start
[10.16.146.17 10.16.146.17] MSG:
Configuration file already exists
[10.16.146.18 10.16.146.18] MSG:
Configuration file already exists
INFO[23:56:30 CST] Refreshing etcd configuration
INFO[23:56:30 CST] Backup etcd data regularly
INFO[23:56:31 CST] Get cluster status
[10.16.146.13 10.16.146.13] MSG:
Cluster will be created.
[10.16.146.15 10.16.146.15] MSG:
Cluster already exists.
[10.16.146.15 10.16.146.15] MSG:
v1.18.6
WARN[00:05:32 CST] Task failed ...
WARN[00:05:32 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"
W0321 00:04:12.601393 14163 version.go:102] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://dl.k8s.io/release/stable-1.txt: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
W0321 00:04:12.601527 14163 version.go:103] falling back to the local client version: v1.18.6
W0321 00:04:12.601756 14163 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[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"
W0321 00:04:12.601393 14163 version.go:102] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://dl.k8s.io/release/stable-1.txt: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
W0321 00:04:12.601527 14163 version.go:103] falling back to the local client version: v1.18.6
W0321 00:04:12.601756 14163 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[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
Usage:
kk add nodes [flags]
Flags:
-f, --filename string Path to a configuration file
-h, --help help for nodes
--skip-pull-images Skip pre pull images
-y, --yes Skip pre-check of the installation
Global Flags:
--debug Print detailed information (default true)
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"
W0321 00:04:12.601393 14163 version.go:102] could not fetch a Kubernetes version from the internet: unable to get URL "https://dl.k8s.io/release/stable-1.txt": Get https://dl.k8s.io/release/stable-1.txt: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
W0321 00:04:12.601527 14163 version.go:103] falling back to the local client version: v1.18.6
W0321 00:04:12.601756 14163 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[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