k8s部署问题解决记录

1 .1cni网络问题导致coredns起不来

NetworkPlugin cni failed to set up pod "coredns-5c98db65d4-fr9nk_kube-system" network: failed to set bridge addr: "cni0" already has an IP address different from 172.21.0.1/24NetworkPlugin cni failed to set up pod "coredns-5c98db65d4-fr9nk_kube-system" network: failed to set bridge addr: "cni0" already has an IP address different from 172.21.0.1/24

解决：k8s集群reset之后，重新发布kube-flannel

flannel的资源限制要关闭，不然，会OOM

1. 2 还有一种coredns起不来，是因为dns解析的问题

nameserver xxx.xxx.xxx.xxx这个值不能为空，否则coredns也起不来

vim /etc/resolv.conf
nameserver 114.114.114.114

systemctl daemon-reload
systemctl restart kubelet

2.k8s  reset之后彻底清除上次初始化

kubeadm reset

iptables -F && iptables -t nat -F && iptables -t mangle -F && iptables -X

systemctl stop kubelet
systemctl stop docker
rm -rf /var/lib/cni/*
rm -rf /var/lib/kubelet/*
rm -rf /etc/cni/*
ifconfig cni0 down
ifconfig flannel.1 down
ifconfig docker0 down
ip link delete cni0
ip link delete flannel.1
systemctl start docker

之后重新kubeadm init