度量尚未可用aws上的度量服务器kubernetes

度量尚未可用aws上的度量服务器kubernetes,kubernetes,Kubernetes,我正在尝试在AWS上启用Metrics Server,并遵循以下步骤 克隆或下载Metrics服务器项目 在编辑器中打开deploy/1.8+/metrics-server-deployment.yaml文件 将以下命令值添加到containers属性中(它应该与image属性处于同一级别) 命令: -/metrics服务器 ---kubelet不安全tls 运行kubectl create-f deploy/1.8+,如Metrics服务器repo上所示,以创建部署、服务等 到目前为止,一切正

我正在尝试在AWS上启用Metrics Server,并遵循以下步骤

  • 克隆或下载Metrics服务器项目

  • 在编辑器中打开deploy/1.8+/metrics-server-deployment.yaml文件

  • 将以下命令值添加到containers属性中(它应该与image属性处于同一级别)

  • 命令:
    -/metrics服务器
    ---kubelet不安全tls

  • 运行kubectl create-f deploy/1.8+,如Metrics服务器repo上所示,以创建部署、服务等
  • 到目前为止,一切正常,我的metrics服务器pod运行正常,但是当我执行
    kubectl top nodes
    时,我得到以下错误

    error: metrics not available yet
    
    当我执行
    kubectl日志[metrics server pod name]-n kube system
    时,我得到了这个

    E0611 14:36:57.527048 1 reststorage.go:129] unable to fetch node metrics for node "ip-172-20-xx-xxx.ec2.internal": no metrics known for node
    
    E0611 14:36:57.527069 1 reststorage.go:129] unable to fetch node metrics for node "ip-172-20-xx-xx.ec2.internal": no metrics known for node
    
    E0611 14:36:57.527075 1 reststorage.go:129] unable to fetch node metrics for node "ip-172-xx-114-xxx.ec2.internal": no metrics known for node
    
    E0611 14:36:57.527079 1 reststorage.go:129] unable to fetch node metrics for node "ip-172-xx-xx-xxx.ec2.internal": no metrics known for node
    
    E0611 14:36:57.527084 1 reststorage.go:129] unable to fetch node metrics for node "ip-172-xx-91-xx.ec2.internal": no metrics known for node
    
    E0611 14:36:57.527088 1 reststorage.go:129] unable to fetch node metrics for node "ip-172-20-xx-xxx.ec2.internal": no metrics known for node
    
    E0611 14:37:26.006830 1 manager.go:111] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:ip-172-xx-36-103.ec2.internal: unable to fetch metrics from Kubelet ip-172-xx-36-103.ec2.internal (172.20.36.xxx): request failed - "401 Unauthorized", response: "Unauthorized", unable to fully scrape metrics from source kubelet_summary:ip-172-xx-65-xx.ec2.internal: unable to fetch metrics from Kubelet ip-172-20-65-xxx.ec2.internal (172.xx.65.xx): request failed - "401 Unauthorized", response: "Unauthorized", unable to fully scrape metrics from source kubelet_summary:ip-172-xx-114-xxx.ec2.internal: unable to fetch metrics from Kubelet ip-172-20-114-223.ec2.internal (172.xx.114.xxx): request failed - "401 Unauthorized", response: "Unauthorized", unable to fully scrape metrics from source kubelet_summary:ip-172-xx-63-xxx.ec2.internal: unable to fetch metrics from Kubelet ip-172-xx-63-xxx.ec2.internal (172.xx.63.xxx): request failed - "401 Unauthorized", response: "Unauthorized", unable to fully scrape metrics from source kubelet_summary:ip-172-xxx-91-xx.ec2.internal: unable to fetch metrics from Kubelet ip-172-xx-91-xxx.ec2.internal (172.xx.91.xxx): request failed - "401 Unauthorized", response: "Unauthorized", unable to fully scrape metrics from source kubelet_summary:ip-172-xxx-96-xxx.ec2.internal: unable to fetch metrics from Kubelet ip-172-xx-96-xxx.ec2.internal (172.xx.96.xxx): request failed - "401 Unauthorized", response: "Unauthorized"]
    

    选项I

    添加
    --kubelet首选地址类型=InternalDNS、InternalIP、ExternalDNS、ExternalIP、主机名

    到您的
    度量服务器部署。yaml
    ,例如

    command:
      - /metrics-server
      - --kubelet-insecure-tls
      - --kubelet-preferred-address-types=InternalDNS,InternalIP,ExternalDNS,ExternalIP,Hostname
    
    如果仍然不起作用,请尝试使用

    选项II

    由于metrics server从coredns解析主机名,请将节点IP添加到coredns configmap

    kubectl edit configmap coredns -n kube-system
    

    apiVersion: v1
    data:
      Corefile: |
        .:53 {
            errors
            health
            hosts {
               192.168.199.100 master.qls.com
               192.168.199.220 worker.qls.com
               fallthrough
            }
            kubernetes cluster.local in-addr.arpa ip6.arpa {
               pods insecure
               upstream
               fallthrough in-addr.arpa ip6.arpa
            }
            prometheus :9153
            forward . /etc/resolv.conf
            cache 30
            loop
            reload
            loadbalance
        }
    kind: ConfigMap
    metadata:
      creationTimestamp: "2019-05-17T12:32:08Z"
      name: coredns
      namespace: kube-system
      resourceVersion: "180"
      selfLink: /api/v1/namespaces/kube-system/configmaps/coredns
      uid: c93e5274-789f-11e9-a0ea-42010a9c0003