kubeadm join timeout

最新推荐文章于 2024-08-01 18:30:42 发布

胖胖胖胖胖虎

最新推荐文章于 2024-08-01 18:30:42 发布

阅读量1k

点赞数

CC 4.0 BY-SA版权

分类专栏： K8S 文章标签： kubernetes

本文链接：https://blog.youkuaiyun.com/qq_15138049/article/details/121273265

K8S 专栏收录该内容

102 篇文章

订阅专栏

该篇内容记录了Kubernetes节点尝试加入集群以及使用kubeadm reset进行重置的详细步骤。在节点加入过程中遇到了文件已存在、端口占用等问题，通过kubeadm reset清理后，节点成功加入了集群。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

[root@hadoop02 kubernetes]# kubeadm join 192.168.153.103:6443 --token d4zd6v.xibtlpcycy8jlb70 --discovery-token-ca-cert-hash sha256:8f7643fc558b209f226eef1633f8008bd37a7ed551af5525e58a6ea38849a5b8
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR FileAvailable--etc-kubernetes-kubelet.conf]: /etc/kubernetes/kubelet.conf already exists
        [ERROR Port-10250]: Port 10250 is in use
        [ERROR FileAvailable--etc-kubernetes-pki-ca.crt]: /etc/kubernetes/pki/ca.crt already exists
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

######################
[root@hadoop02 kubernetes]# kubeadm reset -f
[preflight] Running pre-flight checks
W1111 18:01:10.979491  117572 removeetcdmember.go:80] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /var/lib/dockershim /var/run/kubernetes /var/lib/cni]

The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the "iptables" command.

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

################
[root@hadoop02 kubernetes]# kubeadm join 192.168.153.103:6443 --token d4zd6v.xibtlpcycy8jlb70 --discovery-token-ca-cert-hash sha256:8f7643fc558b209f226eef1633f8008bd37a7ed551af5525e58a6ea38849a5b8
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...

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.

[root@hadoop02 kubernetes]#