I0617 23:29:16.504617 10405 token.go:83] [discovery] Failed to request cluster info, will try again: [Get https://172.19.138.68:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp 172.19.138.68:6443: i/o timeout] I0617 23:29:51.505186 10405 token.go:83] [discovery] ...
Hi, I have created a kubernetes cluster but the kubeadm join returns the error: root@nodo1:~# kubeadm join --token 53762b.7b646ca3e558be4c 10.0.2.15:6443 --discovery-token-ca-cert-hash sha256:40b15a8b5914e531cd938d8635aab0ef9cdf3b977adf5...
6. worker节点在join的时候一直卡在[preflight] Running pre-flight checks 错误原因:在kubeadm join 命令后面加上–v=2 查看日志 Failed to request cluster-info, will try again: Get “https://xxxx:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s”: net/http: request canceled...
[discovery] Failed to request cluster info, will try again: [Get https://192.168.0.101:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: x509: certificate has expired or is not yet valid] 解决方法,设定一个时间服务器同步两台服务器的时间。 $ ntpdate ntp1.aliyun.com...
同样的上面的环境配置、docker 安装、kubeadmin、kubelet、kubectl这些都在Node(192.168.11.12)节点安装配置好过后,我们就可以直接在Node 节点上执行kubeadm join 命令了(上面初始化的时候有) 如果出现下面的错误信息: [discovery] Failed to request cluster info, will try again:[Gethttps://192.168.11.11:6443/api...
[discovery] Failed to request cluster info, will try again: [Get https://192.168.0.101:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: x509: certificate has expired or is not yet valid] 1. 解决方法,设定一个时间服务器同步两台服务器的时间。
6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) I0628 05:04:44.799075 24943 token.go:215] [discovery] Failed to request cluster-info, will try again: Get "https:...
failed to pull image \"registry.k8s.io/pause:3.6\": failed to pull and unpack image \"registry.k8s.io/pause:3.6\": failed to resolve reference \"registry.k8s.io/pause:3.6\": failed to do request: Head \"https://asia-east1-docker.pkg.dev/v2/k8s-artifacts-prod/images/pause/manifest...
kubeadm join --token c1d408.5b9a43bfa2926ddc 192.168.0.232:6443 --discovery-token-ca-cert-hashsha256:66906568e7ca6aafa86cd1e6e1d0dc60721aae8b08f5daff347f6a380e81fd4a #报错如下 Failed to connect to API Server"192.168.0.240:6443":there is no JWSsignedtoken in the clus...
This node has joined the cluster: * Certificate signing request was sent to apiserver and a response was received. * The Kubelet was informed of the new secure connection details. Run 'kubectl get nodes' on the control-plane to see this node join the cluster. 5.2 验证 到master节点运行...