k8s解决 kubectl get pod 查看后No resources found问题

最新推荐文章于 2024-01-29 18:02:30 发布
最新推荐文章于 2024-01-29 18:02:30 发布
阅读量8.3k 收藏 4
点赞数
分类专栏： kubernetes 文章标签： k8s pod
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_44839276/article/details/124489621
版权

1. 创建一个资源

# kubectl create -f nginx-ds.yaml

2. 查看pod显示no resources found

# kubectl get pod
No resources found

3. 查看日志

3.1 查看kube-apiserver日志，无异常

3.2 查看kube-kubelet日志，无异常

3.3 查看kube-scheduler日志如下

查看链接127.0.0.1:8000被拒绝，后来在本地查看并没有8000端口，我的apiserver的端口设置的是8080，可能是kube-scheduler启动脚本端口写错

# tail -f /data/logs/kubernetes/kube-scheduler/scheduler.stdout.log
E0429 09:44:11.299768   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.PodDisruptionBudget: Get http://127.0.0.1:8000/apis/policy/v1beta1/poddisruptionbudgets?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:11.304570   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.PersistentVolume: Get http://127.0.0.1:8000/api/v1/persistentvolumes?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:11.308370   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Node: Get http://127.0.0.1:8000/api/v1/nodes?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:11.308745   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.StorageClass: Get http://127.0.0.1:8000/apis/storage.k8s.io/v1/storageclasses?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:11.310308   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.ReplicationController: Get http://127.0.0.1:8000/api/v1/replicationcontrollers?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:11.311481   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.StatefulSet: Get http://127.0.0.1:8000/apis/apps/v1/statefulsets?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.293511   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Service: Get http://127.0.0.1:8000/api/v1/services?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.297952   48887 reflector.go:125] k8s.io/kubernetes/cmd/kube-scheduler/app/server.go:226: Failed to list *v1.Pod: Get http://127.0.0.1:8000/api/v1/pods?fieldSelector=status.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded&limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.299568   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.PersistentVolumeClaim: Get http://127.0.0.1:8000/api/v1/persistentvolumeclaims?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.300620   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.ReplicaSet: Get http://127.0.0.1:8000/apis/apps/v1/replicasets?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.301799   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.PodDisruptionBudget: Get http://127.0.0.1:8000/apis/policy/v1beta1/poddisruptionbudgets?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.305372   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.PersistentVolume: Get http://127.0.0.1:8000/api/v1/persistentvolumes?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.308955   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Node: Get http://127.0.0.1:8000/api/v1/nodes?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.310113   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.StorageClass: Get http://127.0.0.1:8000/apis/storage.k8s.io/v1/storageclasses?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.311407   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.ReplicationController: Get http://127.0.0.1:8000/api/v1/replicationcontrollers?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:44:12.312201   48887 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.StatefulSet: Get http://127.0.0.1:8000/apis/apps/v1/statefulsets?limit=500&resourceVersion=0: dial tcp 127.0.0.1:8000: connect: connection refused

3.4 查看controller-manager日志如下

链接8000端口也是被拒绝了，这里我的apiserver的端口是8080，可能是controller-manage端口写错

# tail -f /data/logs/kubernetes/kube-controller-manager/controller.stdout.log 
E0429 09:45:25.841916   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:28.981869   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:32.367088   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:35.969067   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:38.060622   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:40.605084   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:42.638763   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:45.856238   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:48.169061   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:50.974880   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:54.336228   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused
E0429 09:45:57.195092   48885 leaderelection.go:324] error retrieving resource lock kube-system/kube-controller-manager: Get http://127.0.0.1:8000/api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: dial tcp 127.0.0.1:8000: connect: connection refused

3.5 查看kube-proxy日志

此处判断可能是没有链接到apiserver导致

# tail -f /data/logs/kubernetes/kube-proxy/proxy.stdout.log 
E0429 09:51:56.124383   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Service: the server rejected our request for an unknown reason (get services)
E0429 09:51:56.125239   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Endpoints: the server rejected our request for an unknown reason (get endpoints)
E0429 09:51:57.126052   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Service: the server rejected our request for an unknown reason (get services)
E0429 09:51:57.126586   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Endpoints: the server rejected our request for an unknown reason (get endpoints)
E0429 09:51:58.128520   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Service: the server rejected our request for an unknown reason (get services)
E0429 09:51:58.129030   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Endpoints: the server rejected our request for an unknown reason (get endpoints)
E0429 09:51:59.130244   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Service: the server rejected our request for an unknown reason (get services)
E0429 09:51:59.130979   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Endpoints: the server rejected our request for an unknown reason (get endpoints)
E0429 09:52:00.132002   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Service: the server rejected our request for an unknown reason (get services)
E0429 09:52:00.134413   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Endpoints: the server rejected our request for an unknown reason (get endpoints)
E0429 09:52:01.134364   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Service: the server rejected our request for an unknown reason (get services)
E0429 09:52:01.135871   48886 reflector.go:125] k8s.io/client-go/informers/factory.go:133: Failed to list *v1.Endpoints: the server rejected our request for an unknown reason (get endpoints)

4. 更改

4.1 更改kube-scheduler启动脚本

# 将8000端口改成8080，我的apiserver端口设置的是8080
# cat kube-scheduler.sh
#!/bin/bash
./kube-scheduler \
  --leader-elect \
  --log-dir /data/logs/kubernetes/kube-scheduler \
  --master http://127.0.0.1:8080 \
  --v 2

4.2 更改controller-manager启动脚本

# 此处将8000端口改成8080
# cat kube-controller-manager.sh
#!/bin/bash
./kube-controller-manager \
  --cluster-cidr 172.7.0.0/16 \
  --leader-elect true \
  --log-dir /data/logs/kubernetes/kube-controller-manager \
  --master http://127.0.0.1:8080 \
  --service-account-private-key-file ./cert/ca-key.pem \
  --service-cluster-ip-range 192.168.0.0/16 \
  --root-ca-file ./cert/ca.pem \
  --v 2

4.3 停止supervisord后在start

 # systemctl stop supervisord.service
 # systemctl start supervisord.service
 # supervisorctl status
etcd-server-7-21                 RUNNING   pid 66496, uptime 0:03:22
kube-apiserver-7-21              RUNNING   pid 66497, uptime 0:03:22
kube-controller-manager-7-21     RUNNING   pid 66499, uptime 0:03:22
kube-kubelet-7-21                RUNNING   pid 66706, uptime 0:03:17
kube-proxy-7-21                  RUNNING   pid 66500, uptime 0:03:22
kube-scheduler-7-21              RUNNING   pid 66501, uptime 0:03:22

5. 查看pod

# kubectl get pod
NAME             READY   STATUS              RESTARTS   AGE
nginx-ds-5q6mh   0/1     ContainerCreating   0          4m13s
nginx-ds-8bpc6   0/1     ContainerCreating   0          4m13s

可以能看到pod资源了，但是查看kub-proxy日志还是3.5描述的错误，继续排查。。。。。。

河 静
关注
  • 0
    点赞
  • 踩
  • 4
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
解决kubectl get pods时报错 No resources found.
行走的IT
03-06 2万+
redis-rc.yaml文件编写完成后进行注册，使用k8s命令kubectl get pods命令无法获取，提示 No resources found. 原因 暂时没有找到，启动什么的无异常，网上搜索后初步判断:systemd 单元文件包含ServiceAccount许可控制器，需要指定所需的签名密钥，详见Gitbub。 解决方案 跳过ServiceAccount(未成功) 打开kube-a...
kubectl-grep:通过匹配名称来过滤Kubernetes资源
05-03
Kubectl Grep 通过匹配名称来过滤Kubernetes资源 要求 Kubernetes 1.17.0以上 Kubectl 1.17.0+ 克鲁0.4.0+ 兼容性 请参阅和以获取支持的版本矩阵。 示例：使用Kubernetes-1.19.x构建的kubectl-grep应该与Kubernetes集群版本1.18、1.19、1.20兼容。 我们为什么需要它？ 与Kubernetes一起玩是我的日常工作，通常我在搜索异常Pod时通过pipe ， grep ，-- --label ，-- --field-selector等搜索Pod，但是键入这么长的命令却很烦人。 更改之前，我们通常通过以下命令过滤Pod， $ kubectl get pods | grep "keyword" $ kubectl get pods -o
kubectl get csr 显示No Resources Found的解决记录
热门推荐
weixin_33695082的博客
08-17 1万+
为什么80%的码农都做不了架构师？>>> ...
springframework.web.servlet.resource.NoResourceFoundException: No static resource favicon.ico.
最新发布
li_tianyang的博客
01-29 2988
springboot 单体项目已请求接口就报这个错误，问题是spring boot没有找到favicon.ico图片资源，所以就抛出了这个异常，很鸡肋，不处理看着难受，处理的话又找不到原因。3、clear maven ，重新启动项目。这里有个小坑，需要彻底地重新加载资源，很多时候是放进去试一下，好像不不行，就认为这个方法不行（我就是这样）2、在项目resources创建static文件夹，把favicon.ico放到文件夹里面。1、随便找一张图片，命名为favicon.ico。
k8s技术遇到的问题1--No resources found.
weixin_44736359的博客
07-02 5824
[root@master ~]# kubectl get nodes No resources found. 解决方法： 所有节点： 1.关闭防火墙： systemctl stop firewalld systemctl disable firewalld 2.关闭selinux： sed -i 's/enforcing/disabled/' /etc/selinux/config setenforce 0 3.关闭swap： swapoff -a 临时 vim /etc/fstab 永
二进制安装K8S kubctl get node 返回No resources found
weixin_47980221的博客
06-08 1437
问题描述：node节点kubelet服务启动成功后，在集群master节点执行命令具体结果如下截图 原因：kubelet设置的cgroups和docker的不一致导致 修改docker的cgroup，在daemon.json文件中增加以下内容： vim /etc/docker/daemon.json "exec-opts": ["native.cgroupdriver=systemd"]...
解决kubectl get pods时 No resources found.问题
weixin_39963973的博客
06-04 1万+
环境：VM VirtualBox  centos 7.4使用yum 直接安装的etcd、docker、kube-apiserver、kube-controller-manager、kube-scheduler、kubelet、kube-proxy创建mysql.rc.yaml执行kubectl create -f mysql.yaml  执行成功。执行kubectl get rc    反馈正常执...
解决kubectl get pods 提示 No resources found
在每次的突破中遇见更好的自己
11-28 4154
解决方法： 1、$ vi /etc/kubernetes/apiserver 2、找到这一行 "KUBE_ADMISSION_CONTROL="--admission_control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ServiceAccount,ResourceQuota"，去掉ServiceAccount，保存退出。 3、重新启动kube-apiserver服务即可 systemctl restar..
kubectl get pods no resourse found...
yuxuan89814的专栏
07-25 1062
[root@localhost data]# kubectl get pods No resources found. [root@localhost data]# 1，确认docker有没有安装 [root@localhost data]# systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.
kubctl get nodes 返回No resources found.解决记录
weixin_33824363的博客
09-18 7120
为什么80%的码农都做不了架构师？>>> ...
openstack虚拟机vip设置，kubectl get cs:No resources found
qq_36163711的博客
05-25 802
问题 主机名 用途 ip master01 keepalived 192.168.7.11 master02 keepalived 192.168.7.6 node05 openstack-controller - - vip 192.168.7.230 在安装kubernetes时候，显示： [root@master01 ~]# kubectl get csr No resources found. 两台虚拟机用来做keepalived，vip可以正常飘，但是当vi
解决k8s的kubectl get cs 显示不健康的问题
06-27
解决k8s的kubectl get cs 显示不健康的问题,k8s故障处理
解决k8s中xxl-job执行器pod重建后无法读取到执行日志的问题
08-24
xxl-job-admin读取执行日志的逻辑为：向执行了该任务的执行器发送请求，让执行器从本地读取执行日志。但在k8s中，即使将本地文件通过nfs独立存储，在pod重建后也通常会因为ip变更，找不到执行器，导致读取不到执行日志。解决方案为单独再部署一个xxl-job-read-log服务，将读日志的请求都转到这个服务上，由这个服务统一读取日志。 具体步骤： 1.将执行日志通过nfs存储到一个统一路径，由于文件名是数据库id，所以不会有覆盖问题。 2.部署xxl-job-read-log服务，在配置文件中设置xxl.job.read.log.path=执行日志统一路径。 3.配置流量转发，将/xxl-job-admin/joblog/logDetailCat请求都转到xxl-job-read-log服务。 即可实现随时查看执行日志，不在依赖执行器。
k8s中pod监控看板
12-15
k8s中pod监控看板
kmem问题造成K8S中pod内存溢出
01-20
问题解决 需要在 kubelet 和 docker 上都将 kmem account 功能关闭。kubelet 需要重新编译。 kubelet 版本是 v1.14 及以上，则可以通过在编译 kubelet 的时候加上 Build Tags 来关闭 $ git clone --branch
阿里云k8s kubectl 一键部署springboot2.5
01-10
阿里云k8s kubectl 一键部署springboot2.5
阿里云k8s kubectl 一键部署vue+nginx
01-10
阿里云k8s kubectl 一键部署vue+nginx
K8S-Back-off restarting failed container
河静
09-11 1万+
K8S： Back-off restarting failed container 问题描述： 在网页k8s上想部署一个云主机，centos，于是乎： 1.创建资源-从表单创建 2.添加参数 3.以特权运行并部署 4.运行后最糟糕的三个红太阳出现了 查看日志显示： 终端日志查看：重启失败 初学很懵逼，百度后解决： 原因： 我从官网pull的centos的image，启动容器后，容器内部没有常驻的前台进程，导致容器启动成功后就退出了，所以才一直重启restarting 类似系统级别的的容器，ce
k8s 命令kubectl运行一个pod得命令应该怎么写
06-09
您可以使用以下命令来运行一个Pod： ``` kubectl run <pod名称> --image=<容器镜像名称> ``` 例如，如果您想要运行一个名为"example-pod"的Pod，使用名为"nginx"的NGINX容器镜像，则命令应如下所示： ``` kubectl run example-pod --image=nginx ``` 请注意，这个命令将会创建一个 Deployment 而不是一个单独的 Pod。如果您需要创建一个单独的 Pod，您可以使用下面的命令： ``` kubectl run <pod名称> --image=<容器镜像名称> --restart=Never ``` 例如： ``` kubectl run example-pod --image=nginx --restart=Never ```

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

河 静

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值