【kubadmin】k8s 节点离群后重新加入清理操作
2023-11-04 本文已影响0人
Bogon
# systemctl stop kubectl
# yum -y remove kubectl cri-tools kubelet kubeadm kubernetes-cni
# rm -rf /etc/kubernetes/
# rm -rf /var/lib/kubelet/
# systemctl stop docker
# rm -rf /kingdee/docker/*
# systemctl start docker
# yum -y install kubectl cri-tools kubelet kubeadm kubernetes-cni
# kubeadm join xx.xx.xx.xx:6443 --token vdhmzq.lbxtx1234pey0xfx --discovery-token-ca-cert-hash
sha256:3351edc18bedxxxxxxxdb0076ad1a89b101318cf5a77046d433c4f2e2f6fefa
[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.