VM重新启动后,Kubelet节点设置为“未就绪”

如何解决VM重新启动后,Kubelet节点设置为“未就绪”

这是我的3个带有节点的VM。我不确定它什么时候会崩溃,但是我认为我的VM关闭时必须重新启动。

NAME                            STATUS     ROLES    AGE   VERSION
tjordy-k8-master.myipname       NotReady   master   99d   v1.17.1
tjordy-k8-worker1.myipname      NotReady   <none>   99d   v1.17.1
tjordy-k8-worker2.myipname      NotReady   <none>   99d   v1.17.1

对此的主要影响是,当我尝试从Pod中获取日志或将Pod端口转发到Pod时,出现连接错误。

error: error upgrading connection: error dialing backend: dial tcp 10.18.223.95:10250: connect: no route to host

这是我的主节点中的描述:

Name:               tjordy-k8-master.myipname
Roles:              master
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=tjordy-k8-master.myipname
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/master=
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /var/run/dockershim.sock
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Thu,14 May 2020 02:23:12 -0700
Taints:             node-role.kubernetes.io/master:NoSchedule
                    node.kubernetes.io/unreachable:NoSchedule
Unschedulable:      false
Lease:
  HolderIdentity:  tjordy-k8-master.myipname
  AcquireTime:     <unset>
  RenewTime:       Sat,15 Aug 2020 11:51:16 -0700
Conditions:
  Type                 Status    LastHeartbeatTime                 LastTransitionTime                Reason              Message
  ----                 ------    -----------------                 ------------------                ------              -------
  NetworkUnavailable   False     Thu,14 May 2020 14:13:24 -0700   Thu,14 May 2020 14:13:24 -0700   WeaveIsUp           Weave pod has set this
  MemoryPressure       Unknown   Sat,15 Aug 2020 11:50:47 -0700   Fri,21 Aug 2020 16:03:03 -0700   NodeStatusUnknown   Kubelet stopped posting node status.
  DiskPressure         Unknown   Sat,21 Aug 2020 16:03:03 -0700   NodeStatusUnknown   Kubelet stopped posting node status.
  PIDPressure          Unknown   Sat,21 Aug 2020 16:03:03 -0700   NodeStatusUnknown   Kubelet stopped posting node status.
  Ready                Unknown   Sat,21 Aug 2020 16:03:03 -0700   NodeStatusUnknown   Kubelet stopped posting node status.
Addresses:
  InternalIP:  10.18.223.22
  Hostname:    tjordy-k8-master.myipname
Capacity:
  cpu:                2
  ephemeral-storage:  100112644Ki
  hugepages-2Mi:      0
  memory:             3880788Ki
  pods:               110
Allocatable:
  cpu:                2
  ephemeral-storage:  92263812558
  hugepages-2Mi:      0
  memory:             3778388Ki
  pods:               110
System Info:
  Machine ID:                 b116c790be914ec08657e4cc260f0164
  System UUID:                4216A453-81C5-3477-2710-CF356A1B0BFE
  Boot ID:                    c73333b0-cd1c-40f2-8877-28a8a4b4bd05
  Kernel Version:             3.10.0-957.10.1.el7.x86_64
  OS Image:                   CentOS Linux 7 (Core)
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  docker://19.3.8
  Kubelet Version:            v1.17.1
  Kube-Proxy Version:         v1.17.1
Non-terminated Pods:          (9 in total)
  Namespace                   Name                                                               CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                   ----                                                               ------------  ----------  ---------------  -------------  ---
  default                     prometheus-operator-1589787700-prometheus-node-exporter-nb4fv      0 (0%)        0 (0%)      0 (0%)           0 (0%)         95d
  kube-system                 coredns-6955765f44-pk8jm                                           100m (5%)     0 (0%)      70Mi (1%)        170Mi (4%)     99d
  kube-system                 coredns-6955765f44-xkfk6                                           100m (5%)     0 (0%)      70Mi (1%)        170Mi (4%)     99d
  kube-system                 etcd-tjordy-k8-master.myipname                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         99d
  kube-system                 kube-apiserver-tjordy-k8-master.myipname             250m (12%)    0 (0%)      0 (0%)           0 (0%)         99d
  kube-system                 kube-controller-manager-tjordy-k8-master.myipname    200m (10%)    0 (0%)      0 (0%)           0 (0%)         99d
  kube-system                 kube-proxy-xcg6h                                                   0 (0%)        0 (0%)      0 (0%)           0 (0%)         99d
  kube-system                 kube-scheduler-tjordy-k8-master.myipname             100m (5%)     0 (0%)      0 (0%)           0 (0%)         99d
  kube-system                 weave-net-6fmv6                                                    20m (1%)      0 (0%)      0 (0%)           0 (0%)         99d
Allocated resources:
  (Total limits may be over 100 percent,i.e.,overcommitted.)
  Resource           Requests    Limits
  --------           --------    ------
  cpu                770m (38%)  0 (0%)
  memory             140Mi (3%)  340Mi (9%)
  ephemeral-storage  0 (0%)      0 (0%)
Events:              <none>

我尝试重新启动它们,但没有任何更改。不太确定该怎么办。

编辑: 运行journalctl -u kubelet。有数千行,但主要特征在于

Aug 21 19:44:42 3nxdomain kubelet[8060]: I0821 19:44:42.158482    8060 kubelet_node_status.go:294] Setting node annotation to enable volume controller attach/detach
Aug 21 19:44:42 3nxdomain kubelet[8060]: E0821 19:44:42.189131    8060 kubelet.go:2263] node "3nxdomain" not found
Aug 21 19:44:42 3nxdomain kubelet[8060]: E0821 19:44:42.289338    8060 kubelet.go:2263] node "3nxdomain" not found
Aug 21 19:44:42 3nxdomain kubelet[8060]: E0821 19:44:42.390437    8060 kubelet.go:2263] node "3nxdomain" not found
Aug 21 19:44:42 3nxdomain kubelet[8060]: I0821 19:44:42.411680    8060 kubelet_node_status.go:70] Attempting to register node 3nxdomain
Aug 21 19:44:42 3nxdomain kubelet[8060]: E0821 19:44:42.413954    8060 kubelet_node_status.go:92] Unable to register node "3nxdomain" with API server: nodes "3nxdomain" is forbidden: node "tjordy-k8-master.myip" is not allowed to modify node "3nxdomain"
Aug 21 19:44:42 3nxdomain kubelet[8060]: E0821 19:44:42.490625    8060 kubelet.go:2263] node "3nxdomain" not found

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
参考1 参考2 解决方案 # 点击安装源 协议选择 http:// 路径填写 mirrors.aliyun.com/centos/8.3.2011/BaseOS/x86_64/os URL类型 软件库URL 其他路径 # 版本 7 mirrors.aliyun.com/centos/7/os/x86
报错1 [root@slave1 data_mocker]# kafka-console-consumer.sh --bootstrap-server slave1:9092 --topic topic_db [2023-12-19 18:31:12,770] WARN [Consumer clie
错误1 # 重写数据 hive (edu)&gt; insert overwrite table dwd_trade_cart_add_inc &gt; select data.id, &gt; data.user_id, &gt; data.course_id, &gt; date_format(
错误1 hive (edu)&gt; insert into huanhuan values(1,&#39;haoge&#39;); Query ID = root_20240110071417_fe1517ad-3607-41f4-bdcf-d00b98ac443e Total jobs = 1
报错1:执行到如下就不执行了,没有显示Successfully registered new MBean. [root@slave1 bin]# /usr/local/software/flume-1.9.0/bin/flume-ng agent -n a1 -c /usr/local/softwa
虚拟及没有启动任何服务器查看jps会显示jps,如果没有显示任何东西 [root@slave2 ~]# jps 9647 Jps 解决方案 # 进入/tmp查看 [root@slave1 dfs]# cd /tmp [root@slave1 tmp]# ll 总用量 48 drwxr-xr-x. 2
报错1 hive&gt; show databases; OK Failed with exception java.io.IOException:java.lang.RuntimeException: Error in configuring object Time taken: 0.474 se
报错1 [root@localhost ~]# vim -bash: vim: 未找到命令 安装vim yum -y install vim* # 查看是否安装成功 [root@hadoop01 hadoop]# rpm -qa |grep vim vim-X11-7.4.629-8.el7_9.x
修改hadoop配置 vi /usr/local/software/hadoop-2.9.2/etc/hadoop/yarn-site.xml # 添加如下 &lt;configuration&gt; &lt;property&gt; &lt;name&gt;yarn.nodemanager.res