当前位置：首页 > news >正文

K8s The connection to the server 192.168.56.120:6443 was refused报错解决

news 来源：原创 2025/6/19 6:06:37

虚拟机获取不到其他node节点的信息，通过使用docker ps -a 排查看到k8s的组件都是exited的状态，通过手动拉起docker 镜像id 起来之后，又变为exited的状态！！！

解决方法：重置k8s集群

使用 kubeadm 重置集群

重置节点：每个节点都要做

[root@k8s-node1 ~]# sudo kubeadm reset
[reset] WARNING: Changes made to this host by 'kubeadm init' or 'kubeadm join' will be reverted.
[reset] Are you sure you want to proceed? [y/N]: y
[preflight] Running pre-flight checks
W0211 17:18:03.552529   46759 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory
[reset] No etcd config found. Assuming external etcd
[reset] Please, manually reset etcd to prevent further issues
[reset] Stopping the kubelet service
[reset] Unmounting mounted directories in "/var/lib/kubelet"
[reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
[reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
[reset] Deleting contents of stateful directories: [/var/lib/kubelet /var/lib/dockershim /var/run/kubernetes /var/lib/cni]

The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d

The reset process does not reset or clean up iptables rules or IPVS tables.
If you wish to reset iptables, you must do so manually by using the "iptables" command.

If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
to reset your system's IPVS tables.

The reset process does not clean your kubeconfig files and you must remove them manually.
Please, check the contents of the $HOME/.kube/config file.

清理网络配置：

sudo rm -rf /etc/cni/net.d

删除 Kubernetes 配置文件：

sudo rm -rf ~/.kube

修改/etc/docker/daemon-reload.json配置：

[root@k8s-node1 ~]# cat /etc/docker/daemon.json 
{
    "registry-mirrors": [
        "https://docker.m.daocloud.io",
        "https://hub-mirror.c.163.com",
        "https://mirror.baidubce.com",
        "https://docker.nju.edu.cn",
	"https://docker.1ms.run"
    ],
     "exec-opts": ["native.cgroupdriver=systemd"]
}

systemctl daemon-reload
systemctl restart docker

重新初始化集群：


kubeadm init \
--apiserver-advertise-address=192.168.9.128 \
--image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers \
--kubernetes-version=v1.21.10 \
--service-cidr=10.96.0.0/16 \
--pod-network-cidr=10.244.0.0/16

执行成功后执行初始化中的命令：

[root@k8s-master ~]#   mkdir -p $HOME/.kube
[root@k8s-master ~]#   sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
[root@k8s-master ~]#   sudo chown $(id -u):$(id -g) $HOME/.kube/config

查看pod状态正在重启：

启动网络插件：

[root@k8s-master ~]# kubectl apply -f calico.yaml

在node节点上执行命令加入集群：

[root@k8s-node1 ~]# kubeadm join 192.168.9.128:6443 --token 8lkkzr.2dfoplpi3qkw8a2i \
> --discovery-token-ca-cert-hash sha256:a1d58ef5642910cd5375f3f6852ec241448ae417c2b075cff213c64f1cc68447 
[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.

查看节点状态：成功解决