记录安装metrics-server遇到的问题（版本v0.3.6）--测试环境

最新推荐文章于 2024-06-24 17:53:03 发布
最新推荐文章于 2024-06-24 17:53:03 发布
阅读量1.1k 收藏
点赞数
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_39073944/article/details/107723198
版权

yaml:
https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/metrics-server

请注意：测试环境

需要修改的地方：

apiVersion: v1
kind: ServiceAccount
metadata:
  name: metrics-server
  namespace: kube-system
  labels:
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: Reconcile
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: metrics-server-config
  namespace: kube-system
  labels:
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: EnsureExists
data:
  NannyConfiguration: |-
    apiVersion: nannyconfig/v1alpha1
    kind: NannyConfiguration
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: metrics-server-v0.3.6
  namespace: kube-system
  labels:
    k8s-app: metrics-server
    kubernetes.io/cluster-service: "true"
    addonmanager.kubernetes.io/mode: Reconcile
    version: v0.3.6
spec:
  selector:
    matchLabels:
      k8s-app: metrics-server
      version: v0.3.6
  template:
    metadata:
      name: metrics-server
      labels:
        k8s-app: metrics-server
        version: v0.3.6
      annotations:
        seccomp.security.alpha.kubernetes.io/pod: 'docker/default'
    spec:
      priorityClassName: system-cluster-critical
      serviceAccountName: metrics-server
      nodeSelector:
        kubernetes.io/os: linux
      containers:
      - name: metrics-server
        image: k8s.gcr.io/metrics-server-amd64:v0.3.6
        #修改镜像拉取方式
        imagePullPolicy: IfNotPresent
        command:
        #加入下列2行代码,解释Flag --deprecated-kubelet-completely-insecure has been deprecated,  
        #This is rarely the right option, since it leaves kubelet communication completely 
        #insecure.  If #you encounter auth errors, make sure you've enabled token webhook auth on 
        #the Kubelet, and if #you're in a test cluster with self-signed Kubelet certificates, 
        #consider using kubelet-insecure-#tls instead.：
        - /metrics-server
        - --metric-resolution=30s
        - --kubelet-insecure-tls
        # These are needed for GKE, which doesn't support secure communication yet.
        # Remove these lines for non-GKE clusters, and when GKE supports token-based auth.
        # 注释该行代码。10255端口已经默认废弃
        #- --kubelet-port=10255
        #注释该行代码
        #- --deprecated-kubelet-completely-insecure=true
        #- --kubelet-preferred-address-types=InternalIP
        - --kubelet-preferred-address-types=InternalIP,Hostname,InternalDNS,ExternalDNS,ExternalIP
        ports:
        - containerPort: 443
          name: https
          protocol: TCP
      - name: metrics-server-nanny
        image: k8s.gcr.io/addon-resizer:1.8.11
        imagePullPolicy: IfNotPresent
        resources:
          limits:
            cpu: 100m
            memory: 300Mi
          requests:
            cpu: 5m
            memory: 50Mi
        env:
          - name: MY_POD_NAME
            valueFrom:
              fieldRef:
                fieldPath: metadata.name
          - name: MY_POD_NAMESPACE
            valueFrom:
              fieldRef:
                fieldPath: metadata.namespace
        volumeMounts:
        - name: metrics-server-config-volume
          mountPath: /etc/config
        command:
          - /pod_nanny
          - --config-dir=/etc/config
          - --cpu=80m
          - --extra-cpu=0.5m
          - --memory=80Mi
          - --extra-memory=80Mi
          - --threshold=5
          - --deployment=metrics-server-v0.3.6
          - --container=metrics-server
          - --poll-period=300000
          - --estimator=exponential
          # Specifies the smallest cluster (defined in number of nodes)
          # resources will be scaled to.
          #- --minClusterSize={{ metrics_server_min_cluster_size }}
          # Use kube-apiserver metrics to avoid periodically listing nodes.
          - --use-metrics=true
      volumes:
        - name: metrics-server-config-volume
          configMap:
            name: metrics-server-config
      tolerations:
        - key: "CriticalAddonsOnly"
          operator: "Exists"

遇到的问题（1）：

```yaml
E0731 14:41:44.340879       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:k8s-ha: unable to fetch metrics from Kubelet k8s-ha (192.168.8.10): Get http://192.168.8.10:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.10:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:master3: unable to fetch metrics from Kubelet master3 (192.168.8.12): Get http://192.168.8.12:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.12:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:master2: unable to fetch metrics from Kubelet master2 (192.168.8.11): Get http://192.168.8.11:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.11:10255: connect: connection refused]
E0731 14:42:14.328932       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:k8s-ha: unable to fetch metrics from Kubelet k8s-ha (192.168.8.10): Get http://192.168.8.10:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.10:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:master2: unable to fetch metrics from Kubelet master2 (192.168.8.11): Get http://192.168.8.11:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.11:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:master3: unable to fetch metrics from Kubelet master3 (192.168.8.12): Get http://192.168.8.12:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.12:10255: connect: connection refused]
E0731 14:42:44.341216       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:master3: unable to fetch metrics from Kubelet master3 (192.168.8.12): Get http://192.168.8.12:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.12:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:k8s-ha: unable to fetch metrics from Kubelet k8s-ha (192.168.8.10): Get http://192.168.8.10:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.10:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:master2: unable to fetch metrics from Kubelet master2 (192.168.8.11): Get http://192.168.8.11:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.11:10255: connect: connection refused]
E0731 14:43:14.327808       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:master3: unable to fetch metrics from Kubelet master3 (192.168.8.12): Get http://192.168.8.12:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.12:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:k8s-ha: unable to fetch metrics from Kubelet k8s-ha (192.168.8.10): Get http://192.168.8.10:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.10:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:master2: unable to fetch metrics from Kubelet master2 (192.168.8.11): Get http://192.168.8.11:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.11:10255: connect: connection refused]
E0731 14:43:44.340386       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:master3: unable to fetch metrics from Kubelet master3 (192.168.8.12): Get http://192.168.8.12:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.12:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:master2: unable to fetch metrics from Kubelet master2 (192.168.8.11): Get http://192.168.8.11:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.11:10255: connect: connection refused, unable to fully scrape metrics from source kubelet_summary:k8s-ha: unable to fetch metrics from Kubelet k8s-ha (192.168.8.10): Get http://192.168.8.10:10255/stats/summary?only_cpu_and_memory=true: dial tcp 192.168.8.10:10255: connect: connection refused]

解决办法： 注释以下条目

  • –kubelet-port=10255

遇到的问题（2）：

E0731 14:13:35.439656       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:master2: unable to fetch metrics from Kubelet master2 (192.168.8.11): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n", unable to fully scrape metrics from source kubelet_summary:k8s-ha: unable to fetch metrics from Kubelet k8s-ha (192.168.8.10): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n", unable to fully scrape metrics from source kubelet_summary:master3: unable to fetch metrics from Kubelet master3 (192.168.8.12): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n"]
E0731 14:14:05.428724       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:master2: unable to fetch metrics from Kubelet master2 (192.168.8.11): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n", unable to fully scrape metrics from source kubelet_summary:k8s-ha: unable to fetch metrics from Kubelet k8s-ha (192.168.8.10): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n", unable to fully scrape metrics from source kubelet_summary:master3: unable to fetch metrics from Kubelet master3 (192.168.8.12): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n"]
E0731 14:14:35.440679       1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:master3: unable to fetch metrics from Kubelet master3 (192.168.8.12): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n", unable to fully scrape metrics from source kubelet_summary:k8s-ha: unable to fetch metrics from Kubelet k8s-ha (192.168.8.10): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n", unable to fully scrape metrics from source kubelet_summary:master2: unable to fetch metrics from Kubelet master2 (192.168.8.11): request failed - "400 Bad Request", response: "Client sent an HTTP request to an HTTPS server.\n"]

解决办法：
注释：- --deprecated-kubelet-completely-insecure=true

weixin_39073944
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
k8s1.6安装metrics-server-amd64:v0.3.6
wangchao_cn的专栏
12-19 2969
# 下载metrics镜像，k8s.gcr.io/metrics-server-amd64:v0.3.6下载不了 docker pull htcfive/metrics-server-amd64:v0.3.6 # 下载配置文件 git clone https://github.com/kubernetes-incubator/metrics-server # 进入1.8配置文件目...
Linux Kubernetes 资源监控 Metrics-Server V0.3.6 部署与应用
weixin_45029822的博客
08-21 687
Metrics-Server V0.3.6 部署与应用一、Metrics-Server的部署二、 Metrics-Server 的使用 一、Metrics-Server的部署 Metrics-Server是集群核心监控数据的聚合器，用来替换之前的heapster。 容器相关的 Metrics 主要来自于 kubelet 内置的 cAdvisor 服务，有了Metrics-Server之后，用户就可以通过标准的 Kubernetes API 来访问到这些监控数据。 Metrics API 只可以查询当前的度.
metrics-server最新版本有坑，慎用
weixin_33757609的博客
05-28 3273
参考文档：https://www.jianshu.com/p/262177fa9320 版本：metrics-server-amd64:v0.3.3 addon-resizer:1.8.4 [root@master metrics]# vim metrics-server-deployment.yaml 查看： 莫名其妙的一对报错，不错最终搞好了。 毫...
K8S安装metrics-server
codelearning的专栏
06-24 1617
于 Kubernetes，Metrics API 提供了一组基本的指标，以支持自动伸缩和类似的用例。该 API 提供有关节点和 Pod 的资源使用情况的信息， 包括 CPU 和内存的指标。如果将 Metrics API 部署到集群中， 那么 Kubernetes API 的客户端就可以查询这些信息，并且可以使用 Kubernetes 的访问控制机制来管理权限。(HPA) 和(VPA) 使用 metrics API 中的数据调整工作负载副本和资源，以满足客户需求。
【云原生】kubernetes v1.18部署Metrics-Server:v0.3.6
我是小bā吖的博客
04-13 475
介绍 Metrics Server 前首先介绍一下 Heapster，该工具是用于 Kubernetes 集群监控和性能分析工具，可以收集节点上的指标数据，例如，节点的 CPU、Memory、Network 和 Disk 的 Metric 数据。不过在 Kubernetes V1.11 版本后将被逐渐废弃。而 Metrics Server 正是 Heapster 的代替者。
K8S安装metrics-server(v0.3.6)
Little Prince H的博客
02-22 596
K8S安装metrics-server(v0.3.6) 一、前提条件 注意：使用 Metrics Server 有必备两个条件： 1、API Server 启用 Aggregator Routing 支持。 Error from server (ServiceUnavailable): the server is currently unable to handle the request (get pods.metrics.k8s.io) 2、API Server 能访问 Metrics Server
addon-resizer_1.8.3 & metrics-server-amd64_v0.3.1.zip
03-06
addon-resizer_1.8.3 ， metrics-server-amd64_v0.3.1.zip
metrics-server v0.6.1镜像包和安装文件
03-07
metrics-server v0.6.1镜像包和安装文件
metrics-server v0.5.2镜像包和安装文件
01-27
metrics-server v0.5.2镜像包和安装文件
k8s-gcr-io-metrics-server-metrics-server-v0.4.1.rar
12-14
k8s.gcr.io/metrics-server/metrics-server:v0.4.1 components.yaml 博客地址：https://blog.csdn.net/shenhonglei1234/category_7260434.html
k8s资源监控组件metrics-server离线镜像 v0.7.1版本
最新发布
07-20
加载方式： docker load -i metrics-server.v0.7.1.tar
metrics-server-on-rancher-2.0.2:通过Rancher部署的集群在Kubernetes上设置Metrics-Server的方法
05-13
在Rancher中托管的现有Kubernetes群集上设置Metrics Server 问题 由于不赞成使用Heapster而采用了Metrics-Server，一些Kubernetes的默认设置发生了变化。 Metrics-Server还需要Heapster不需要的TLS证书CA文件。 解决方案摘要 其中之一 修改节点定义，以确保集群与度量服务器兼容。 修复现有节点以支持metrics-server。 更多信息 这种方法是改编自从 。 设置 修改集群定义 注意本文档的此部分适用于配备了IaaS支持的Rancher节点驱动程序（即Azure，EC2，Digital Ocean）的群集。 未通过云提供商Rancher节点驱动程序（即AKS，EKS，GKE）进行设置，也未通过导入或自定义工作流程创建。 您可能仍需要修改集群。 使用此文档作为指南，但是由于Rancher并未创建您的集群，因此
metrics-server-v0.50.tar
07-06
metrics-server-v0.50.tar
kubernetes(k8s)中部署metrics-server遇到的问题
Nick学习PHP的点点滴滴
05-31 8939
个人博客原文：kubernetes(k8s)中部署metrics-server遇到的问题 metrics-server版本：k8s.gcr.io/metrics-server-amd64:v0.3.3 k8s版本：v1.14.1 The '--source' flag is unavailable right now (v0.3.0-alpha.1) containers: - name...
k8s通过Kuboard安装Metrics server报错的解决办法
qq_34168515的博客
05-15 5782
文章目录通过Kuboard安装Metrics server确认 metrics-server 是否正常运行确认 ApiService 是否正常排查步骤1，根据ApiService的日志，查443端口排查步骤2，metrics-server pod日志 查4443端口解决，既然443端口访问不了，那么久访问4443，改造server顺利解决 通过Kuboard安装Metrics server 出现的问题可以参考官网：https://kuboard.cn/install/faq/metrics-server.h
kubernetes(k8s)监控组件metrics-server安装
张飞的博客
11-24 3276
一、下载安装需要的yaml文件 metrics-server的官网：https://github.com/kubernetes-sigs/metrics-server 在github上面有metrics-server的安装步骤： 但是如果直接使用这条命令安装的话会因为k8s.gcr.io在国内网络下无法安装metrics-server的镜像而失败。所以我下载的不是最新版，而是v0.3.6。首先下载需要的componenets.yaml文件： wget https://github.com/kubernet
安装metrics-server
weixin_45387943的博客
03-03 3139
安装metrics-server会踩无数的坑，网上搜出来的教程要么看不懂，要么没用，要么复杂，只看博主这一个就可以了。 1.在安装之前最好先镜像一下，防止手残，回滚是最方便的。 2.首先查看自己是否安装过git如果有，请yum remove git 卸载掉重新安装,保证是新版 yum remove git yum install git -y 3.获取metrics-server, 注意使用的版本,我这里使用的是3.6版本的 git clone -b v0.3.6 https://github.com/
Metrics Server 配置和安全注意事项
firmament0422的博客
10-26 303
Metrics Server 配置
K8s validating data: the server could not find the requested resource ... with --validate=false
cab5的博客
05-18 6103
背景 最近公司升级了k8s环境，导致在客户端执行 kubectl create -f ${file_name}.yaml 或者 kubectl replace -f ${file_name}.yaml 的时候报错，如下： error validating data: the server could not find the requested resource; if you choose to ignore these errors, turn validation off with --vali
在虚拟机中怎样安装 metrics-server
06-12
要在虚拟机中安装 metrics-server，可以按照以下步骤进行操作： 1. 下载 metrics-server 的 YAML 文件。可以使用以下命令从 GitHub 上下载最新版本的 YAML 文件： ``` $ wget ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值