一起来学k8s 07.安装metrics-server和heapster

最新推荐文章于 2025-04-22 10:13:26 发布
原创 最新推荐文章于 2025-04-22 10:13:26 发布 · 1.3k 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#kubernetes

本文介绍如何在Kubernetes集群中部署Metrics Server和Heapster，以获取和监控节点及Pod的资源使用情况，包括详细的步骤和常见问题解决办法。

Metrics-Server

Kubernetes从1.8版本开始，CPU、内存等资源的metrics信息可以通过 Metrics API来获取，用户可以直接获取这些metrics信息

环境

192.168.48.101 master01
192.168.48.201 node01
192.168.48.202 node02

Metrics API

  1. 通过Metrics API我们可以获取到指定node或者pod的当前资源使用情况，API本身不存储任何信息，所以我们不可能通过API来获取资源的历史使用情况。
  2. Metrics API的获取路径位于：/apis/metrics.k8s.io/
  3. 获取Metrics API的前提条件是metrics server要在K8S集群中成功部署
  4. 更多的metrics资料请参考：<https://github.com/kubernetes/metrics>

Metrics Install

由于官方已经弃用heapster，现metrics-server作为其替代方案，当前最新版本为v0.3.3

官方项目地址

https://github.com/kubernetes-incubator/metrics-server

下载项目

git clone https://github.com/kubernetes-incubator/metrics-server

yaml文件在/root/metrics-server/deploy/1.8+

[root@master01 ~]# cd metrics-server/deploy/1.8+/
[root@master01 1.8+]# ls
aggregated-metrics-reader.yaml  auth-delegator.yaml  auth-reader.yaml  metrics-apiservice.yaml  metrics-server-deployment.yaml  metrics-server-service.yaml  resource-reader.yaml

修改yaml文件，添加参数

vim metrics-server-deployment.yaml

- name: metrics-server
        image: k8s.gcr.io/metrics-server-amd64:v0.3.3
        imagePullPolicy: IfNotPresent
        args:
          - --kubelet-preferred-address-types=InternalIP,Hostname,InternalDNS,ExternalDNS,ExternalIP
          - --kubelet-insecure-tls

在这里插入图片描述

Metrics镜像

k8s.gcr.io/metrics-server-amd64:v0.3.3

镜像下载

链接: https://pan.baidu.com/s/12d-2XTzw1gwLR52erGQ9hg 提取码: yxan

导入Metrics镜像

docker load -i metrics-0.3.3.tar.gz

创建Metrics

[root@master01 ~]# cd metrics-server/deploy/1.8+/
[root@master01 1.8+]# kubectl apply -f .
clusterrole.rbac.authorization.k8s.io/system:aggregated-metrics-reader created
clusterrolebinding.rbac.authorization.k8s.io/metrics-server:system:auth-delegator created
rolebinding.rbac.authorization.k8s.io/metrics-server-auth-reader created
apiservice.apiregistration.k8s.io/v1beta1.metrics.k8s.io created
serviceaccount/metrics-server created
deployment.extensions/metrics-server created
service/metrics-server created
clusterrole.rbac.authorization.k8s.io/system:metrics-server created
clusterrolebinding.rbac.authorization.k8s.io/system:metrics-server created

[root@master01 1.8+]# kubectl get pod -n kube-system 
NAME                                    READY   STATUS    RESTARTS   AGE
coredns-fb8b8dccf-jfm2m                 1/1     Running   3          8d
coredns-fb8b8dccf-r8tqp                 1/1     Running   3          8d
etcd-master                             1/1     Running   2          8d
kube-apiserver-master                   1/1     Running   2          8d
kube-controller-manager-master          1/1     Running   2          8d
kube-flannel-ds-amd64-26xjf             1/1     Running   3          8d
kube-flannel-ds-amd64-82s7n             1/1     Running   3          8d
kube-flannel-ds-amd64-sd2j9             1/1     Running   3          8d
kube-proxy-792hk                        1/1     Running   2          8d
kube-proxy-88cgt                        1/1     Running   3          8d
kube-proxy-frgtq                        1/1     Running   2          8d
kube-scheduler-master                   1/1     Running   2          8d
kubernetes-dashboard-5f7b999d65-9v5f9   1/1     Running   0          46m
metrics-server-c9f69c698-c7zl9          1/1     Running   0          5s

验收

部署成功后，达到如下结果，则为正常：

[root@master01 ~]# kubectl top nodes 
NAME     CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
master   86m          4%     963Mi           25%       
node01   26m          1%     522Mi           13%       
node02   21m          1%     503Mi           13%       

[root@master01 ~]# kubectl top pods --all-namespaces
NAMESPACE     NAME                                    CPU(cores)   MEMORY(bytes)   
default       demo-deploy-8675c97685-vhncn            0m           2Mi             
default       demo-deploy-8675c97685-w7md2            0m           2Mi             
default       demo-pod                                0m           4Mi             
kube-system   coredns-fb8b8dccf-jfm2m                 2m           13Mi            
kube-system   coredns-fb8b8dccf-r8tqp                 2m           13Mi            
kube-system   etcd-master                             13m          71Mi            
kube-system   kube-apiserver-master                   18m          297Mi           
kube-system   kube-controller-manager-master          9m           50Mi            
kube-system   kube-flannel-ds-amd64-26xjf             2m           12Mi            
kube-system   kube-flannel-ds-amd64-82s7n             2m           17Mi            
kube-system   kube-flannel-ds-amd64-sd2j9             2m           18Mi            
kube-system   kube-proxy-792hk                        1m           17Mi            
kube-system   kube-proxy-88cgt                        1m           19Mi            
kube-system   kube-proxy-frgtq                        1m           16Mi            
kube-system   kube-scheduler-master                   1m           15Mi            
kube-system   kubernetes-dashboard-5f7b999d65-9v5f9   1m           11Mi            
kube-system   metrics-server-c9f69c698-c7zl9          1m           13Mi

Heapster

目前dashboard插件如果想在界面上显示资源使用率，它还依赖于heapster；另外，测试发现k8s 1.8版本的kubectl top也依赖heapster，因此建议补充安装heapster，无需安装influxdb和grafana。

准备heapster.yaml

vim heapster.yaml

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: heapster
  namespace: kube-system
---

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: heapster
subjects:
  - kind: ServiceAccount
    name: heapster
    namespace: kube-system
roleRef:
  kind: ClusterRole
  name: system:heapster
  apiGroup: rbac.authorization.k8s.io
---

apiVersion: apps/v1beta1
kind: Deployment
metadata:
  name: heapster
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: heapster
  template:
    metadata:
      labels:
        task: monitoring
        k8s-app: heapster
    spec:
      serviceAccountName: heapster
      containers:
      - name: heapster
        image: k8s.gcr.io/heapster-amd64:v1.5.4
        imagePullPolicy: IfNotPresent
        command:
        - /heapster
        #- --source=kubernetes:https://kubernetes.default
        - --source=kubernetes.summary_api:''
        #- --sink=influxdb:http://monitoring-influxdb.kube-system.svc:8086
        livenessProbe:
          httpGet:
            path: /healthz
            port: 8082
            scheme: HTTP
          initialDelaySeconds: 180
          timeoutSeconds: 5
---
apiVersion: v1
kind: Service
metadata:
  labels:
    task: monitoring
    # For use as a Cluster add-on (https://github.com/kubernetes/kubernetes/tree/master/cluster/addons)
    # If you are NOT using this as an addon, you should comment out this line.
    #kubernetes.io/cluster-service: 'true'
    kubernetes.io/name: Heapster
  name: heapster
  namespace: kube-system
spec:
  ports:
  - port: 80
    targetPort: 8082
  selector:
    k8s-app: heapster

heapster镜像

k8s.gcr.io/heapster-amd64:v1.5.4

镜像下载

链接：https://pan.baidu.com/s/1an-hA1hhsbbIGaLGgPYd-Q 提取码：n0dw

导入heapster镜像

 dockerl load -i heapster-1.5.4.tar.gz

创建heapster

[root@master01 ~]# kubectl apply -f heapster.yaml 
serviceaccount/heapster created
clusterrolebinding.rbac.authorization.k8s.io/heapster created
deployment.apps/heapster created
service/heapster created

[root@master01 ~]# kubectl get pod -n kube-system -o wide
NAME                                    READY   STATUS    RESTARTS   AGE   IP               NODE     NOMINATED NODE   READINESS GATES
coredns-fb8b8dccf-jfm2m                 1/1     Running   5          8d    10.244.0.9       master01   <none>           <none>
coredns-fb8b8dccf-r8tqp                 1/1     Running   4          8d    10.244.0.10      master01   <none>           <none>
etcd-master01                             1/1     Running   3          8d    192.168.48.200   master01   <none>           <none>
heapster-587f9c9f8b-rfgsc               1/1     Running   0          76s   10.244.2.7       node02   <none>           <none>
kube-apiserver-master01                   1/1     Running   3          8d    192.168.48.200   master01   <none>           <none>
kube-controller-manager-master01          1/1     Running   3          8d    192.168.48.200   master01   <none>           <none>
kube-flannel-ds-amd64-26xjf             1/1     Running   4          8d    192.168.48.200   master01   <none>           <none>
kube-flannel-ds-amd64-82s7n             1/1     Running   3          8d    192.168.48.201   node01   <none>           <none>
kube-flannel-ds-amd64-sd2j9             1/1     Running   3          8d    192.168.48.202   node02   <none>           <none>
kube-proxy-792hk                        1/1     Running   3          8d    192.168.48.200   master01   <none>           <none>
kube-proxy-88cgt                        1/1     Running   3          8d    192.168.48.201   node01   <none>           <none>
kube-proxy-frgtq                        1/1     Running   2          8d    192.168.48.202   node02   <none>           <none>
kube-scheduler-master                   1/1     Running   3          8d    192.168.48.200   master01   <none>           <none>
kubernetes-dashboard-5f7b999d65-9v5f9   1/1     Running   0          84m   10.244.1.6       node01   <none>           <none>
metrics-server-c9f69c698-c7zl9          1/1     Running   0          38m   10.244.1.7       node01   <none>           <none>

结果发现dashboard并没有生成图形
在这里插入图片描述

查看日志

[root@master01 ~]# kubectl logs -n kube-system heapster-587f9c9f8b-rfgsc 
I0408 13:00:46.262981       1 heapster.go:78] /heapster --source=kubernetes.summary_api:''
I0408 13:00:46.263011       1 heapster.go:79] Heapster version v1.5.4
I0408 13:00:46.263200       1 configs.go:61] Using Kubernetes client with master "https://10.96.0.1:443" and version v1
I0408 13:00:46.263210       1 configs.go:62] Using kubelet port 10255
I0408 13:00:46.263834       1 heapster.go:202] Starting with Metric Sink
I0408 13:00:46.270800       1 heapster.go:112] Starting heapster on port 8082
E0408 13:01:05.003469       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.200:10255: Get http://192.168.48.200:10255/stats/summary/: dial tcp 192.168.48.200:10255: getsockopt: connection refused
E0408 13:01:05.007752       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.202:10255: Get http://192.168.48.202:10255/stats/summary/: dial tcp 192.168.48.202:10255: getsockopt: connection refused
E0408 13:01:05.022308       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.201:10255: Get http://192.168.48.201:10255/stats/summary/: dial tcp 192.168.48.201:10255: getsockopt: connection refused
W0408 13:01:25.000727       1 manager.go:152] Failed to get all responses in time (got 0/3)
E0408 13:02:05.013965       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.202:10255: Get http://192.168.48.202:10255/stats/summary/: dial tcp 192.168.48.202:10255: getsockopt: connection refused
E0408 13:02:05.016730       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.200:10255: Get http://192.168.48.200:10255/stats/summary/: dial tcp 192.168.48.200:10255: getsockopt: connection refused
E0408 13:02:05.017933       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.201:10255: Get http://192.168.48.201:10255/stats/summary/: dial tcp 192.168.48.201:10255: getsockopt: connection refused
W0408 13:02:25.001764       1 manager.go:152] Failed to get all responses in time (got 0/3)
E0408 13:03:05.008722       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.202:10255: Get http://192.168.48.202:10255/stats/summary/: dial tcp 192.168.48.202:10255: getsockopt: connection refused
E0408 13:03:05.019129       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.201:10255: Get http://192.168.48.201:10255/stats/summary/: dial tcp 192.168.48.201:10255: getsockopt: connection refused
E0408 13:03:05.019318       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.200:10255: Get http://192.168.48.200:10255/stats/summary/: dial tcp 192.168.48.200:10255: getsockopt: connection refused
W0408 13:03:25.001723       1 manager.go:152] Failed to get all responses in time (got 0/3)
E0408 13:04:05.004438       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.200:10255: Get http://192.168.48.200:10255/stats/summary/: dial tcp 192.168.48.200:10255: getsockopt: connection refused
E0408 13:04:05.004837       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.201:10255: Get http://192.168.48.201:10255/stats/summary/: dial tcp 192.168.48.201:10255: getsockopt: connection refused
E0408 13:04:05.017424       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.202:10255: Get http://192.168.48.202:10255/stats/summary/: dial tcp 192.168.48.202:10255: getsockopt: connection refused
W0408 13:04:25.001505       1 manager.go:152] Failed to get all responses in time (got 0/3)
E0408 13:05:05.004518       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.201:10255: Get http://192.168.48.201:10255/stats/summary/: dial tcp 192.168.48.201:10255: getsockopt: connection refused
E0408 13:05:05.006935       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.202:10255: Get http://192.168.48.202:10255/stats/summary/: dial tcp 192.168.48.202:10255: getsockopt: connection refused
E0408 13:05:05.007187       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.200:10255: Get http://192.168.48.200:10255/stats/summary/: dial tcp 192.168.48.200:10255: getsockopt: connection refused
W0408 13:05:25.001816       1 manager.go:152] Failed to get all responses in time (got 0/3)
E0408 13:06:05.009242       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.202:10255: Get http://192.168.48.202:10255/stats/summary/: dial tcp 192.168.48.202:10255: getsockopt: connection refused
E0408 13:06:05.019315       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.201:10255: Get http://192.168.48.201:10255/stats/summary/: dial tcp 192.168.48.201:10255: getsockopt: connection refused
E0408 13:06:05.024390       1 manager.go:101] Error in scraping containers from kubelet_summary:192.168.48.200:10255: Get http://192.168.48.200:10255/stats/summary/: dial tcp 192.168.48.200:10255: getsockopt: connection refused

原因10255端口没开，所有节点都要开启10255端口，添加readOnlyPort: 10255

vim /var/lib/kubelet/config.yaml
.....
port: 10250
readOnlyPort: 10255
registryBurst: 10
registryPullQPS: 5
resolvConf: /etc/resolv.conf

重启kubelet

[root@master01 ~]# systemctl daemon-reload 
[root@master01 ~]# systemctl restart kubelet.service
[root@master01 ~]# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:45028         0.0.0.0:*               LISTEN      58103/kubelet       
tcp        0      0 127.0.0.1:10248         0.0.0.0:*               LISTEN      58103/kubelet       
tcp        0      0 127.0.0.1:10249         0.0.0.0:*               LISTEN      43472/kube-proxy    
tcp        0      0 192.168.48.200:2379     0.0.0.0:*               LISTEN      43426/etcd          
tcp        0      0 127.0.0.1:2379          0.0.0.0:*               LISTEN      43426/etcd          
tcp        0      0 192.168.48.200:2380     0.0.0.0:*               LISTEN      43426/etcd          
tcp        0      0 127.0.0.1:10257         0.0.0.0:*               LISTEN      43368/kube-controll 
tcp        0      0 127.0.0.1:10259         0.0.0.0:*               LISTEN      43343/kube-schedule 
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      951/sshd            
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1034/master         
tcp6       0      0 :::30080                :::*                    LISTEN      43472/kube-proxy    
tcp6       0      0 :::10250                :::*                    LISTEN      58103/kubelet       
tcp6       0      0 :::10251                :::*                    LISTEN      43343/kube-schedule 
tcp6       0      0 :::6443                 :::*                    LISTEN      43325/kube-apiserve 
tcp6       0      0 :::10252                :::*                    LISTEN      43368/kube-controll 
tcp6       0      0 :::10255                :::*                    LISTEN      58103/kubelet       
tcp6       0      0 :::10256                :::*                    LISTEN      43472/kube-proxy    
tcp6       0      0 :::30001                :::*                    LISTEN      43472/kube-proxy    
tcp6       0      0 :::22                   :::*                    LISTEN      951/sshd            
tcp6       0      0 ::1:25                  :::*                    LISTEN      1034/master         
[root@master ~]#

重启heapster

[root@master ~]# kubectl delete -f heapster.yaml 
serviceaccount "heapster" deleted
clusterrolebinding.rbac.authorization.k8s.io "heapster" deleted
deployment.apps "heapster" deleted
service "heapster" deleted

[root@master ~]# kubectl apply -f heapster.yaml 
serviceaccount/heapster created
clusterrolebinding.rbac.authorization.k8s.io/heapster created
deployment.apps/heapster created
service/heapster created

验收

经过一段时间收集，图形界面已出
在这里插入图片描述
在这里插入图片描述

【k8s源码分析-Apiserver-1】理解 apiserver 的结构（AggregatorServer、KubeAPIServer、ApiExtensionsServer）
叮当猫的喵i
12-06 1097
Prometheus 项目与Kubernetes项目一样，也来自于 Google 的Borg体系，它的原型系统，叫作 BorgMon，是一个几乎与 Borg 同时诞生的内部监控系统。而 Prometheus 项目的发起原因也跟 Kubernetes 很类似，都是希望通过对用户更友好的方式，将 Google 内部系统的设计理念，传递给用户和开发者。作为一个监控系统，Prometheus 项目的作用和工作方式，其实可以用如下所示的一张官方示意图来解释。可以看到，Prometheus 项目工作的核心，是。
Kubernetes安装metrics-server
engchina的专栏
09-08 448
kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.3.7/components.yaml
在 Kubernetes (k8s) 中安装 Metrics Server
2302_78308374的博客
03-31 1268
以指定 Metrics Server 在与 Kubelet 通信时的地址类型优先级。如果需要高可用性配置（至少需要两个节点），可以下载高可用版本的 YAML 文件。1、下载 Metrics Server 的部署文件。如果在国内，可能需要替换镜像地址。二、安装 Metrics Server。2、修改 YAML 文件（如果需要）替换为可用的镜像地址，如。以跳过 TLS 证书验证。
k8s || metrics server
qq_60271706的博客
03-27 1951
Metrics Server 是 Kubernetes 内置自动缩放管道的可扩展、高效的容器资源指标来源。Metrics Server 从 Kubelets 收集资源指标，并通过 Metrics API 在 Kubernetes apiserver 中公开它们，以供 Horizontal Pod Autoscaler 和Vertical Pod Autoscaler 使用。Metrics API 也可以通过访问 kubectl top，从而更容易调试自动缩放管道。
二十五、Kubernetes安装metrics-server详解、实例
全栈行动派的博客
01-13 3543
Kubernetes安装metrics-server详解、实例
使用Heapster获取集群对象的metric数据
weixin_33714884的博客
04-11 174
2019独角兽企业重金招聘Python工程师标准>>> ...
k8s-部署metrics-server + Prometheus
热门推荐
wangmiaoyan的博客
09-17 2万+
部署metrics-server+prometheus+grafana
Kubernetes学习之Metrics-Server
Micky_Yang的博客
09-26 1405
一、资源监控 　　Kubernetes有多个数据指标需要采集相关的数据，而这些指标大体上可以分为两个组成部分：监控集体本身和监控Pod对象，在集群监控层面，目标是监控整个Kubernetes集群的健康状况，包括集群中的所有工作节点是否运行正常、系统资源容量大小、每个工作节点上运行的容器化应用的数量以及整个集群的资源利用率等等，它们通常可以分为如下一些可衡量的指标。 　　1）节点资源状态：这个领域的众多指标都与资源利用状况有关，主要有网络带宽、磁盘空间、CPU和内存的利用率；基于这些度量指标，管理员能够评估集
K8S 安装Metrics Server
ふりこ细工の心
03-17 389
前言 初次使用hpa 的时候发现始终无法使用起来，在网上查了半天发现是需要安装Metrics Server的 php-apache Deployment/php-apache <unknown>/50% 1 10 1 61s 下面是我对照着参考链接部署过程，相对比较顺利，写这篇文章用于做笔记 参考 https://blog.csdn.net/nklinsirui/article/details/109413053 一、Metr
基于Custom-metrics-apiserver实现Kubernetes的HPA（内含踩坑）
编程知识分享
06-09 1993
前言 这里要说一下Prometheus的检控指标从哪里来，它有3个渠道： 主机监控，也就是部署了Node Exporter组件的主机，它以DaemonSet或者系统进程的形式运行，Prometheus会从这里获取关于宿主机相关的资源指标 从Kubernetes自身组件，比如API Server或者Kubelet的/metrics，可以获取工作队列长度、请求QPS以及kubelet...
230. k8s_v1.15监控小插件（heapster）
Kason_iWiki
08-06 434
文章目录1.准备heapster镜像2.准备资源配置清单3.应用资源配置清单4.重启dashboard heapster官方github地址https://github.com/kubernetes-retired/heapster 1.准备heapster镜像 运维主机HDSS7-200.host.com操作： [root@hdss7-200 ~]# docker pull quay.io/bitnami/heapster:1.5.4 [root@hdss7--200 ~]# docker tag c35
k8s基础学习--metrics和hespster监控部署
weixin_30537391的博客
04-21 192
最近在K8S上部署监控工具Heapster和Metrics遇到一些问题。pod启动之后显示： [root@MASTER ~]# kubectl top nodeError from server (ServiceUnavailable): the server is currently unable to handle the request (get nodes.metrics.k8s.io)...
k8s-容器资源需求、资源限制及HeapSter-二十二
weixin_30525825的博客
03-25 319
一、容器资源需求、资源限制 资源需求、资源限制：指的是cpu、内存等资源； 资源需求、资源限制的两个关键字： request：需求，最低保障，在调度时，这个节点必须要满足request需求的资源大小； limits：限制、硬限制。这个限制容器无论怎么运行都不会超过limits的值； CPU：k8s的一个cpu对应一颗宿主机逻辑cpu。一个逻辑cpu还可以划分为1000个毫核（mi...
pod mysql扩展安装_在kubernetes中安装heapster或metric服务器以进行水平pod自动扩展
weixin_31164189的博客
02-02 93
您需要先下载以下文件：curl https://raw.githubusercontent.com/kubernetes/heapster/master/deploy/kube-config/influxdb/grafana.yaml > grafana.yamlcurl https://raw.githubusercontent.com/kubernetes/heapster/master...
[error]: dial tcp :6379: connect: connection refused
西卡卡的博客
04-13 6503
转载自：https://forum.chirpstack.io/t/error-redis-connection-error-dial-tcp-myip-connect-connection-refused/3799 [error]: dial tcp :6379: connect: connection refused change to bind 0.0.0.0，And dont forget to restart redis server
k8s dashboard 集成heapster pod资源监控界面
u010955999的博客
04-09 3406
k8s dashboard的界面中仅显示了pod一些配置信息以及node层面的监控，无法图形化展现集群度量指标信息。下图为dashboard界面：而如果要展示图形化的集群度量指标信息，就需要安装一个dashboard插件：heapster。Heapster原生支持K8s(v1.0.6及以后版本)和CoreOS，并且支持多种存储后端，比如：InfluxDB、ElasticSearch、Kafka等，...
K8S里如何部署性能监控组件metrics server
zhangli_perdue的博客
01-22 2358
K8S从1.7版本开始引入metrics server替代heapster，原因是heapster无法提供符合K8S标准的API。使用metrics server，就可以通过K8S API获取到监控指标。本文大部分参考K8S官方的metrics server部署文档（https://github.com/kubernetes-incubator/metrics-server），部分地方做了一定修改...
【Metrics Server安装（Prometheus无法抓取Metrics）】
dmonsterer的博客
01-20 121
原文：https://blog.csdn.net/hezuijiudexiaobai/article/details/144684274。
k8s-1.28.10 安装metrics-server
最新发布
liudongyang123的博客
04-22 566
Metrics Server是一个集群范围的资源使用情况的数据聚合器。作为一个应用部署在集群中。Metric server从每个节点上KubeletAPI收集指标，通过Kubernetes聚合器注册在Master APIServer中。为集群提供Node、Pods资源利用率指标。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值