简体   繁体   English

从Kubelet和cri-o获取Pod统计信息时出现问题

[英]Problem getting pods stats from kubelet and cri-o

We are running Kubernetes with the following configuration: On-premise Kubernetes 1.11.3, cri-o 1.11.6 and CentOS7 with UEK-4.14.35 我们正在使用以下配置运行Kubernetes:本地Kubernetes 1.11.3,cri-o 1.11.6和带有UEK-4.14.35的CentOS7

I can't make crictl stats to return pods information, it returns empty list only. 我无法通过crictl统计信息来返回广告连播信息,它仅返回空列表。 Has anyone run into the same problem? 有人遇到过同样的问题吗?

Another issue we have, is that when I query the kubelet for stats/summary it returns an empty pods list. 我们遇到的另一个问题是,当我查询kubelet的统计信息/摘要时,它将返回一个空的pod列表。

I think that these two issues are related, although I am not sure which one of them is the problem. 我认为这两个问题是相关的,尽管我不确定哪个是问题。

I would recommend checking kubelet service to verify health status and debug any suspicious events within the cluster. 我建议检查kubelet服务以验证运行状况并调试集群中的任何可疑事件。 I assume that CRI-O runtime engine can select kubelet as the main Pods information provider because of its managing Pod lifecycle role. 我假设CRI-O运行时引擎可以选择kubelet作为Pods的主要信息提供者,因为它具有Pod生命周期管理角色。

systemctl status kubelet -l

journalctl -u kubelet

In case you found some errors or dubious events, share it in a comment below this answer. 如果您发现一些错误或可疑事件,请在此答案下方的评论中分享。

However, you can use metrics-server , which will collect Pod metrics in the cluster and enable kube-apiserver flags for Aggregation Layer . 但是,您可以使用metrics-server ,它将收集集群中的Pod度量并为Aggregation Layer启用kube-apiserver标志。 Here is a good article about Horizontal Pod Autoscaling and monitoring resources via Prometheus . 这是一篇关于水平Pod自动缩放和通过Prometheus监视资源的好文章

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Kubernetes 与 CRI-O 和 docker 私有注册表:仅在主节点上运行的 Pod - Kubernetes with CRI-O and docker private registry: pods running only on master node 在 K8S 集群中切换容器运行时。 从 CRI-O 到 docker - Switch container runtime in K8S cluster. From CRI-O to docker 是否可以在 containerd/kubernetes CRI-O 中运行葡萄酒? - Is it possible to run wine in containerd/ kubernetes CRI-O? 当 `cgroup_manager=systemd` 时使用 cri-o 运行 pod 和容器 - use cri-o to run pod and container when `cgroup_manager=systemd` cri-o 套接字 (crio.sock) 与 dockershim 套接字 (dockershim.sock) - cri-o socket (crio.sock) vs dockershim socket (dockershim.sock) 我的 Pod 获得 SIGTERM 并作为信号处理程序的一部分正常退出,但无法找到为什么 SIGTERM 从 kubelet 发送到我的 pod 的根本原因? - My Pods getting SIGTERM and exited gracefully as part of signalhandler but unable to find root cause of why SIGTERM sent from kubelet to my pods? 为什么kubelet无法从docker获取统计信息(错误500)? - Why do kubelet failed to get stats from docker (error 500)? kubelet 无法获取 docker 和 kubelet 服务的 cgroup 统计信息 - kubelet fails to get cgroup stats for docker and kubelet services 通过Prometheus从多个Kubernetes容器中刮取自定义统计信息 - Scraping custom stats from multiple Kubernetes pods via Prometheus 很多 kubelet 错误:无法更新容器的统计信息 - A lot of kubelet errors : Failed to update stats for container
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM