k8s 1.10.26 一次containerd失败引发kubectl不可用问题

k8s 1.10.26 一次containerd失败引发kubectl不可用问题

开机k8s 1.10.26时,报以下错误

bash 复制代码
[root@master ~]# kubectl get no
E0515 08:03:00.914894    7993 memcache.go:265] couldn't get current server API group list: Get "https://192.168.80.50:6443/api?timeout=32s": dial tcp 192.168.80.50:6443: connect: connection refused
E0515 08:03:00.915787    7993 memcache.go:265] couldn't get current server API group list: Get "https://192.168.80.50:6443/api?timeout=32s": dial tcp 192.168.80.50:6443: connect: connection refused
E0515 08:03:00.917903    7993 memcache.go:265] couldn't get current server API group list: Get "https://192.168.80.50:6443/api?timeout=32s": dial tcp 192.168.80.50:6443: connect: connection refused
E0515 08:03:00.920028    7993 memcache.go:265] couldn't get current server API group list: Get "https://192.168.80.50:6443/api?timeout=32s": dial tcp 192.168.80.50:6443: connect: connection refused
E0515 08:03:00.922527    7993 memcache.go:265] couldn't get current server API group list: Get "https://192.168.80.50:6443/api?timeout=32s": dial tcp 192.168.80.50:6443: connect: connection refused
The connection to the server 192.168.80.50:6443 was refused - did you specify the right host or port?

查看kubelet状态

bash 复制代码
 kubelet.service - kubelet: The Kubernetes Node Agent
   Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor pre>
  Drop-In: /usr/lib/systemd/system/kubelet.service.d
           └─10-kubeadm.conf
   Active: activating (auto-restart) (Result: exit-code) since Thu 2025-05-15 0>
     Docs: https://kubernetes.io/docs/
  Process: 8114 ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CO>
 Main PID: 8114 (code=exited, status=1/FAILURE)

查看日志 journalctl -xu kubelet

关键日志:

启动container查看报错

journalctl -xe

● containerd.service - containerd container runtime Loaded: loaded

(/usr/lib/systemd/system/containerd.service; disabled; vendor>

Active: inactive (dead)

Docs: https://containerd.io

解决:

排查发现,配置文件有问题

bash 复制代码
systemctl stop containerd.service

cp /etc/containerd/config.toml /etc/containerd/config.toml.bak
sudo containerd config default > $HOME/config.toml
sudo cp $HOME/config.toml /etc/containerd/config.toml
sudo sed -i "s#registry.k8s.io/pause#registry.cn-hangzhou.aliyuncs.com/google_containers/pause#g" /etc/containerd/config.toml

sudo sed -i "s#SystemdCgroup = false#SystemdCgroup = true#g" /etc/containerd/config.toml

#启动containerd

启动kubelet

bash 复制代码
systemctl start kubelet
systemctl status kubelet

问题解决。

get node 正常。

相关推荐
运维栈记1 小时前
虚拟化网络的根基-网络命名空间
网络·docker·容器
lbb 小魔仙2 小时前
【Linux】云原生运维效率提升:Linux 终端工具链(kubectl + tmux + fzf)组合拳教程
linux·运维·云原生
Joren的学习记录2 小时前
【Linux运维大神系列】Kubernetes详解3(kubeadm部署k8s1.23高可用集群)
linux·运维·kubernetes
Hellc0072 小时前
Docker网络冲突排查与解决方案:完整指南
网络·docker·容器
hanyi_qwe3 小时前
发布策略 【K8S (三)】
docker·容器·kubernetes
眠りたいです3 小时前
Docker核心技术和实现原理第二部分:docker镜像与网络原理
运维·网络·docker·容器
Mr. Cao code4 小时前
Docker数据管理:持久化存储最佳实践
java·docker·容器
Cyber4K6 小时前
【Kubernetes专项】DockerFile、数据持计划、网络模式及资源配额
运维·网络·云原生·容器·kubernetes
Joren的学习记录7 小时前
【Linux运维疑难杂症】k8s集群创建calico网络失败
linux·运维·kubernetes
鲨莎分不晴7 小时前
Docker 网络深度解析:打破容器的“孤岛效应”
网络·docker·容器