前一次 init 时，master ip 写错了，导致init 失败，修改IP后再次执行时，报 kubeadm init 失败，port is in use
Last login: Thu Oct 13 15:11:27 2022 from 172.16.0.66 [root@k8smaster ~]# kubeadm init \ > --apiserver-advertise-address=192.168.1.181 \ > --image-repository registry.aliyuncs.com/google_containers \ > --kubernetes-version v1.18.19 \ > --service-cidr=10.96.0.0/12 \ > --pod-network-cidr=10.244.0.0/16 W1013 15:57:48.682495 48352 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io] [init] Using Kubernetes version: v1.18.19 [preflight] Running pre-flight checks [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/ [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service' error execution phase preflight: [preflight] Some fatal errors occurred: [ERROR Port-10259]: Port 10259 is in use [ERROR Port-10257]: Port 10257 is in use [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists [ERROR Port-10250]: Port 10250 is in use [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@k8smaster ~]# ^C [root@k8smaster ~]#
解决方法
[root@k8smaster ~]# kubeadm reset
