Error log:
[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 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=...`
The reason is: some configuration files and services already exist
Solution:
#reset kubeadm
kubeadm reset
After running the kubeadm join command
or
Cause: There are residual files
Solution: (works)
#Delete k8s configuration file and certificate file
rm -rf /etc/kubernetes/kubelet.conf /etc/kubernetes/pki/ca.crt #Delete k8s configuration file and certificate file
#
kubeadm join 192.168.191.133:6443 --token xvnp3x.pl6i8ikcdoixkaf0 \
--discovery-token-ca-cert-hash sha256:9f90161043001c0c75fac7d61590734f844ee507526e948f3647d7b9cfc1362dSimilar Posts:
- [Solved] kubeadm join 192.168.50.66:6443 –token 0109we.c3a3ofn0y0lmp0w9 –discovery-token-ca-cert-hash sha256:262f5eefdbeba51e6875cba5ed6e34061ad679f8a21f6e295d9fbd5ef05757e4
- The newly deployed k8s cluster of the virtual machine reports an error when executing kubectl logs and exec
- K8S Error: no metrics known for node [How to Solve]
- Other Master Nodes Add to the Cluster After Reset Error: CONTEXT DEADLINE EXCEEDED
- Error already running as process when starting zookeeper
- VIM edit prompt swap file already exists solution
- [Solved] kuberlet Service Startup Error: “Failed to run kubelet” err=”failed to run Kubelet: misconfiguration: kubelet cgroup driver: \”systemd\” is different from docker cgroup driver: \”cgroupfs\””
- 413 errors are reported in the service exposed by ingress
- Xcode Package Archive Error: Command /usr/bin/codesign failed
- [Solved] error C2275: ‘TOKEN’ : illegal use of this type as an expression