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 正常。

相关推荐
阿里云云原生17 小时前
Agent 数据飞轮平台的选型和实践
云原生
做运维的阿瑞18 小时前
云项目可观测性与成本治理:告警、日志、Dashboard 与预算标签
大数据·云原生·云计算·terraform
无人生还别怕19 小时前
如何搭建k8s服务(containerd部署)
linux·云原生·容器·kubernetes·openanolisos
知已难寻19 小时前
01 · OpenStack的认证管理 Keystone
运维·服务器·云原生·云计算·openstack
分布式存储与RustFS20 小时前
模型权重散落在每台 GPU?用 RustFS 给 vLLM 做共享权重库
云原生·开源·对象存储·分布式存储·s3·rustfs·性能基准
木雷坞20 小时前
Baserow Docker部署:导入设备借用CSV,再用表单新增登记
运维·docker·容器
fb_1234521 小时前
从探针到权限:一篇吃透 Kubernetes 健康检查、RBAC 认证授权与 Dashboard 可视化管理
云原生·容器·kubernetes
wefg121 小时前
【Docker】基本指令
运维·docker·容器
mengge.cloud1 天前
10-28-Kubernetes健康检查认证授权与Dashboard
云原生·容器·kubernetes
做运维的阿瑞1 天前
EKS 可销毁环境:集群创建、应用部署到账单归零
云原生·云计算·terraform