一次kubeadm init后的傻操作
k8s join 节点记录自己超级傻的一次经历,我kubeadm init后,在从节点kubeadm join成功然后,傻操作就来了,我在master节点也join了,然后就:[ERROR DirAvailable--etc-kubernetes-manifests]: /etc/kubernetes/manifests is not empty[ERROR FileAvailable--etc-
·
k8s join 节点
记录自己超级傻的一次经历,我kubeadm init后,在从节点kubeadm join成功
然后,傻操作就来了,我在master节点也join了,然后就:
[ERROR DirAvailable--etc-kubernetes-manifests]: /etc/kubernetes/manifests is not empty
[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
然后我就根据网上资料(搜的时候意识到都是从节点的join问题,可恶呀(-。-;),就。。。
kubeadm reset -f
and then:
kubectl get nodes
出现没权限的错误,然后我就重置了k8s环境,重装了一遍
¯_(ツ)_/¯谁知道我经历了什么,就这样往往复复,也许这就是看着文档不思考的结果,明明成功了,最后又被自己搞坏了
以下记录自己重置k8s的流程(☻-☻):
kubeadm reset -f
modprobe -r ipip
lsmod
rm -rf ~/.kube/
rm -rf /etc/kubernetes/
rm -rf /etc/systemd/system/kubelet.service.d
rm -rf /etc/systemd/system/kubelet.service
rm -rf /usr/bin/kube*
rm -rf /etc/cni
rm -rf /opt/cni
rm -rf /var/lib/etcd
rm -rf /var/etcd
yum remove -y kubelet kubeadm kubectl
yum install -y kubelet kubeadm kubectl && systemctl enable kubelet
更多推荐
已为社区贡献3条内容
所有评论(0)