指标服务器在部署期间没有已知的 pod 错误指标 [英] metrics-server no metrics known for pod error during deployment

查看:42
本文介绍了指标服务器在部署期间没有已知的 pod 错误指标的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个新创建的 AWS EKS 1.18 集群,应用程序部署在上面,一切正常,测试和负载测试成功,即我的 HPA 和指标服务器工作正常.

I have a newly created AWS EKS 1.18 Cluster, applications are deployed on it, everything is fine, test and load test are successful, namely, my HPA and metrics-server is working fine.

但是当我对服务进行部署时,metrics-server 正在提供无法获取 pod xxx 的 pod 指标:对于新部署的 pod,没有已知的 pod 指标,然后问题正在解决,一切又正常了.

But when I make a deployment to a service, metrics-server is giving unable to fetch pod metrics for pod xxx: no metrics known for pod for the newly deployed pod, then problem is being resolved and everything is fine again.

我的问题是,这是指标服务器的预期行为吗?还是我应该再次检查我的配置?

My question is, is this an expected behaviour for metrics-server? Or should I check my configs again?

非常感谢.

推荐答案

有一个 评论 在 github 上:

There is a comment about that on github:

Metrics Server 预计报告没有已知的 pod 指标";直到缓存将被填充.新部署的指标服务器上的缓存可能为空,也可能会丢失新部署的 pod 的值.

Metrics Server is expected to report "no metrics known for pod" until cache will be populated. Cache can be empty on freshly deployed metrics-server or can miss values for newly deployed pods.

因此,如果我理解正确,它会按预期工作.我认为这个问题在 60 年代后通过 默认 指标每 60 秒抓取一次.

So if I understand correctly it's working as expected. I assume this problem is being solved after 60s as by default metrics are scraped every 60s.

这篇关于指标服务器在部署期间没有已知的 pod 错误指标的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆