今天就跟大家聊聊有關(guān)metrics-server的示例分析，可能很多人都不太了解，為了讓大家更加了解，小編給大家總結(jié)了以下內(nèi)容，希望大家根據(jù)這篇文章可以有所收獲。

成都創(chuàng)新互聯(lián)公司主要業(yè)務(wù)有網(wǎng)站營(yíng)銷策劃、網(wǎng)站設(shè)計(jì)制作、成都網(wǎng)站制作、微信公眾號(hào)開發(fā)、成都小程序開發(fā)、H5頁(yè)面制作、程序開發(fā)等業(yè)務(wù)。一次合作終身朋友，是我們奉行的宗旨；我們不僅僅把客戶當(dāng)客戶，還把客戶視為我們的合作伙伴，在開展業(yè)務(wù)的過程中，公司還積累了豐富的行業(yè)經(jīng)驗(yàn)、成都全網(wǎng)營(yíng)銷推廣資源和合作伙伴關(guān)系資源，并逐漸建立起規(guī)范的客戶服務(wù)和保障體系。 

1 下載項(xiàng)目

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

2 修改配置文件

cd /root/metrics-server/deploy/1.8+



[root@master 1.8+]# vim metrics-server-deployment.yaml 

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: metrics-server
  namespace: kube-system
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: metrics-server
  namespace: kube-system
  labels:
    k8s-app: metrics-server
spec:
  selector:
    matchLabels:
      k8s-app: metrics-server
  template:
    metadata:
      name: metrics-server
      labels:
        k8s-app: metrics-server
    spec:
      serviceAccountName: metrics-server
      volumes:
      # mount in tmp so we can safely use from-scratch images and/or read-only containers
      - name: tmp-dir
        emptyDir: {}
      containers:
      - name: metrics-server
        image: k8s.gcr.io/metrics-server-amd64:v0.3.1
        imagePullPolicy: Always
        command:
        - /metrics-server
        - --kubelet-insecure-tls
        - --kubelet-preferred-address-types=InternalIP
        volumeMounts:
        - name: tmp-dir
          mountPath: /tmp



增加配置
        command:
        - /metrics-server
        - --kubelet-insecure-tls
        - --kubelet-preferred-address-types=InternalIP

3 應(yīng)用配置文件

 kubectl apply -f .

4 查看pod

# kubectl get pod -n kube-system
NAME                              READY   STATUS    RESTARTS   AGE
calico-node-j85f7                 2/2     Running   2          3h7m
calico-node-tbvs4                 2/2     Running   2          3h4m
calico-node-zwsts                 2/2     Running   2          3h5m
calico-typha-55968bfd7b-zv9vc     1/1     Running   1          3h7m
coreDNS-fb8b8dccf-227fk           1/1     Running   0          54m
coredns-fb8b8dccf-xwscm           1/1     Running   0          54m
etcd-master                       1/1     Running   1          3h21m
kube-apiserver-master             1/1     Running   1          3h21m
kube-controller-manager-master    1/1     Running   1          3h21m
kube-proxy-ltwbd                  1/1     Running   0          55m
kube-proxy-qgrvg                  1/1     Running   0          55m
kube-proxy-xnd45                  1/1     Running   0          55m
kube-scheduler-master             1/1     Running   1          3h21m
metrics-server-58db9f9647-sxtv9   1/1     Running   0          6m42s

5 使用

# kubectl top node
NAME     CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
master   189m         4%     911Mi           24%       
node1    98m          2%     432Mi           5%        
node2    117m         2%     442Mi           5%        
# kubectl top pods
NAME                       CPU(cores)   MEMORY(bytes)   
net-test-7d6d58cc8-8r28m   0m           1Mi             
net-test-7d6d58cc8-k5qdm   0m           1Mi             
# kubectl top pods -n kube-system
NAME                              CPU(cores)   MEMORY(bytes)   
calico-node-j85f7                 29m          59Mi            
calico-node-tbvs4                 25m          61Mi            
calico-node-zwsts                 27m          60Mi            
calico-typha-55968bfd7b-zv9vc     9m           29Mi            
coredns-fb8b8dccf-227fk           4m           13Mi            
coredns-fb8b8dccf-xwscm           4m           13Mi            
etcd-master                       25m          69Mi            
kube-apiserver-master             34m          270Mi           
kube-controller-manager-master    16m          57Mi            
kube-proxy-ltwbd                  1m           17Mi            
kube-proxy-qgrvg                  1m           17Mi            
kube-proxy-xnd45                  1m           18Mi            
kube-scheduler-master             2m           15Mi            
metrics-server-58db9f9647-sxtv9   2m           14Mi

6 查看Metrics API數(shù)據(jù)

啟動(dòng)一個(gè)代理以便curl api

kubectl proxy --port=8080

#直接查看接口數(shù)據(jù)：
#可獲取的資源：nodes和pods
# curl localhost:8080/apis/metrics.k8s.io/v1beta1

 curl localhost:8080/apis/metrics.k8s.io/v1beta1/
{
  "kind": "APIResourceList",
  "apiVersion": "v1",
  "groupVersion": "metrics.k8s.io/v1beta1",
  "resources": [
    {
      "name": "nodes",
      "singularName": "",
      "namespaced": false,
      "kind": "NodeMetrics",
      "verbs": [
        "get",
        "list"
      ]
    },
    {
      "name": "pods",
      "singularName": "",
      "namespaced": true,
      "kind": "PodMetrics",
      "verbs": [
        "get",
        "list"
      ]
    }
  ]
}

看完上述內(nèi)容，你們對(duì)metrics-server的示例分析有進(jìn)一步的了解嗎？如果還想了解更多知識(shí)或者相關(guān)內(nèi)容，請(qǐng)關(guān)注創(chuàng)新互聯(lián)行業(yè)資訊頻道，感謝大家的支持。