【问题标题】:Disabling heapster health checks in Kubernetes 1.10在 Kubernetes 1.10 中禁用 heapster 健康检查
【发布时间】:2019-03-25 09:31:25
【问题描述】:

在做 kubectl cluster-info dump 时,我看到了很多:

2018/10/18 14:47:47 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2018/10/18 14:48:17 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2018/10/18 14:48:47 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2018/10/18 14:49:17 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2018/10/18 14:49:47 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2018/10/18 14:50:17 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2018/10/18 14:50:47 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.

也许这是一个将在新版本中修复的错误(heapster 在新版本中无论如何都已弃用),但无论如何要禁用这些检查以避免这些嘈杂的消息。

【问题讨论】:

  • 我还有一个:I1022 04:16:08.129640 1 wrap.go:42] GET /api/v1/namespaces/kube-system/services/heapster/proxy/healthz: (20.207558ms) 404,但没有任何与heapster相关的资源

标签: kubernetes heapster


【解决方案1】:

您可以找到 Heapster 弃用时间表 here

我发现在 Kubernetes 集群 1.10 版本 kubernetes-dashboard Pod 中会产生这样的错误信息:

kubectl --namespace=kube-system log <kubernetes-dashboard-Pod>

2018/10/22 13:04:36 Metric 客户端健康检查失败:服务器 找不到请求的资源(获取服务堆)。 30 秒后重试。

似乎kubernetes-dashboard 仍然需要 Heapster 服务来实现指标和图形目的。

【讨论】:

  • 谢谢,是的,后来我注意到这是由于仪表板,它也应该在仪表板中被禁用
猜你喜欢
  • 1970-01-01
  • 2020-04-19
  • 1970-01-01
  • 1970-01-01
  • 2018-02-27
  • 2019-01-06
  • 2021-06-15
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多