碼上快樂

相關內容    簡體    繁體

K8S-Metrics Server

本文轉載自   查看原文   2021-12-02 21:52   123    K8S

K8S版本：1.17.11

官網：https://kubernetes.io/docs/tasks/debug-application-cluster/resource-metrics-pipeline/#metrics-server

Metrics Server YAML: https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.3.6

kubectl autoscale 自動控制在k8s集群中運行的pod數量(水平自動伸縮)，需要提前設置pod范圍及觸發條件。
k8s從1.1版本開始增加了名稱為HPA(Horizontal Pod Autoscaler)的控制器，用於實現基於pod中資源
(CPU/Memory)利用率進行對pod的自動擴縮容功能的實現，早期的版本只能基於Heapster組件實現對CPU利用率
做為觸發條件，但是在k8s 1.11版本開始使用Metrices Server完成數據采集，然后將采集到的數據通過
API（Aggregated API，匯總API），例如metrics.k8s.io、custom.metrics.k8s.io、external.metrics.k8s.io，然后
再把數據提供給HPA控制器進行查詢，以實現基於某個資源利用率對pod進行擴縮容的目的。

控制管理器默認每隔15s（可以通過–horizontal-pod-autoscaler-sync-period修改）查詢metrics的資源使用
情況.
支持以下三種metrics指標類型：
　　->預定義metrics（比如Pod的CPU）以利用率的方式計算
　　->自定義的Pod metrics，以原始值（raw value）的方式計算
　　->自定義的object metrics

支持兩種metrics查詢方式：
　　->Heapster
　　->自定義的REST API
　　->支持多metrics

Kubernetes Metrics Server：

  • Kubernetes Metrics Server 是 Cluster 的核心監控數據的聚合器，kubeadm 默認是不部署的。

  • Metrics Server 供 Dashboard 等其他組件使用，是一個擴展的 APIServer，依賴於 API Aggregator。所以，在安裝 Metrics Server 之前需要先在 kube-apiserver 中開啟 API Aggregator。

  • Metrics API 只可以查詢當前的度量數據，並不保存歷史數據。

  • Metrics API URI 為 /apis/metrics.k8s.io/，在 k8s.io/metrics 下維護。

  • 必須部署 metrics-server 才能使用該 API，metrics-server 通過調用 kubelet Summary API 獲取數據。

檢查 API Server 是否開啟了 Aggregator Routing：查看 API Server 是否具有 --enable-aggregator-routing=true 選項。

1.8+]# ps -ef | grep apiserver
root       2824   2683 10 12月01 ?      02:27:19 kube-apiserver --advertise-address=192.168.64.110 --allow-privileged=true --authorization-mode=Node,RBAC --client-ca-file=/etc/kubernetes/pki/ca.crt 
--enable-admission-plugins=NodeRestriction --enable-bootstrap-token-auth=true --etcd-cafile=/etc/kubernetes/pki/etcd/ca.crt --etcd-certfile=/etc/kubernetes/pki/apiserver-etcd-client.crt 
--etcd-keyfile=/etc/kubernetes/pki/apiserver-etcd-client.key --etcd-servers=https://127.0.0.1:2379 --insecure-port=0 --kubelet-client-certificate=/etc/kubernetes/pki/apiserver-kubelet-client.crt 
--kubelet-client-key=/etc/kubernetes/pki/apiserver-kubelet-client.key --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.crt 
--proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client.key --requestheader-allowed-names=front-proxy-client,system:metrics-server,metrics-server --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt
 --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6443 --service-account-key-file=/etc/kubernetes/pki/sa.pub 
--service-cluster-ip-range=10.96.0.0/12 --tls-cert-file=/etc/kubernetes/pki/apiserver.crt --tls-private-key-file=/etc/kubernetes/pki/apiserver.key --enable-aggregator-routing=true
root      68993  40840  0 21:37 pts/0    00:00:00 grep --color=auto apiserver

修改每個 API Server 的 kube-apiserver.yaml 配置開啟 Aggregator Routing：修改 manifests 配置后 API Server 會自動重啟生效

]# cat /etc/kubernetes/manifests/kube-apiserver.yaml
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  labels:
    component: kube-apiserver
    tier: control-plane
  name: kube-apiserver
  namespace: kube-system
spec:
  containers:
  - command:
    - kube-apiserver
    - --advertise-address=192.168.64.110
    - --allow-privileged=true
    - --authorization-mode=Node,RBAC
    - --client-ca-file=/etc/kubernetes/pki/ca.crt
    - --enable-admission-plugins=NodeRestriction
    - --enable-bootstrap-token-auth=true
    - --etcd-cafile=/etc/kubernetes/pki/etcd/ca.crt
    - --etcd-certfile=/etc/kubernetes/pki/apiserver-etcd-client.crt
    - --etcd-keyfile=/etc/kubernetes/pki/apiserver-etcd-client.key
    - --etcd-servers=https://127.0.0.1:2379
    - --insecure-port=0
    - --kubelet-client-certificate=/etc/kubernetes/pki/apiserver-kubelet-client.crt
    - --kubelet-client-key=/etc/kubernetes/pki/apiserver-kubelet-client.key
    - --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname
    - --proxy-client-cert-file=/etc/kubernetes/pki/front-proxy-client.crt
    - --proxy-client-key-file=/etc/kubernetes/pki/front-proxy-client.key
    - --requestheader-allowed-names=front-proxy-client,system:metrics-server,metrics-server
    - --requestheader-client-ca-file=/etc/kubernetes/pki/front-proxy-ca.crt
    - --requestheader-extra-headers-prefix=X-Remote-Extra-
    - --requestheader-group-headers=X-Remote-Group
    - --requestheader-username-headers=X-Remote-User
    - --secure-port=6443
    - --service-account-key-file=/etc/kubernetes/pki/sa.pub
    - --service-cluster-ip-range=10.96.0.0/12
    - --tls-cert-file=/etc/kubernetes/pki/apiserver.crt
    - --tls-private-key-file=/etc/kubernetes/pki/apiserver.key
    - --enable-aggregator-routing=true   //開啟 Aggregator Routing

clone代碼

]# git clone  -b  v0.3.6   https://github.com/kubernetes-sigs/metrics-server.git

獲取指標數據

kubectl top nodes #報錯如下
Error from server (NotFound): the server could not find the requested resource (get services http:heapster:)

准備所需鏡像

# docker pull k8s.gcr.io/metrics-server-amd64:v0.3.6 #google鏡像倉庫
# docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-server-amd64:v0.3.6 #阿里雲鏡像倉庫

修改Metrics-Server配置文件

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: metrics-server
  namespace: kube-system
---
apiVersion: apps/v1
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:
      - name: tmp-dir
        emptyDir: {}
      containers:
      - name: metrics-server
        image: mirrorgooglecontainers/metrics-server-amd64:v0.3.6
        imagePullPolicy: IfNotPresent
        # 添加數據
        command:
        - /metrics-server
        - --kubelet-insecure-tls
        - --kubelet-preferred-address-types=InternalIP
        volumeMounts:
        - name: tmp-dir
          mountPath: /tmp
        resources:
          limits:
            cpu: 300m
            memory: 200Mi
          requests:
            cpu: 200m
            memory: 100Mi

修改完成后部署

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.apps/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

查看

1.8+]# kubectl  get pod -A
NAMESPACE              NAME                                             READY   STATUS    RESTARTS   AGE
kube-system            coredns-6955765f44-8vsfj                         1/1     Running   28         323d
kube-system            coredns-6955765f44-fqt6n                         1/1     Running   28         323d
kube-system            etcd-master                                      1/1     Running   74         323d
kube-system            kube-apiserver-master                            1/1     Running   10         102d
kube-system            kube-controller-manager-master                   1/1     Running   37         323d
kube-system            kube-flannel-ds-64qdh                            1/1     Running   16         323d
kube-system            kube-flannel-ds-d2g8j                            1/1     Running   28         323d
kube-system            kube-flannel-ds-qmssw                            1/1     Running   29         323d
kube-system            kube-proxy-4vkl5                                 1/1     Running   28         323d
kube-system            kube-proxy-mls6g                                 1/1     Running   29         323d
kube-system            kube-proxy-t4xmg                                 1/1     Running   16         323d
kube-system            kube-scheduler-master                            1/1     Running   38         323d
kube-system            metrics-server-d8669575f-xl6mw                   1/1     Running   0          15s
kubernetes-dashboard   dashboard-metrics-scraper-7b8b58dc8b-757sw       1/1     Running   11         102d
kubernetes-dashboard   kubernetes-dashboard-75fdb885bf-kj4kf            1/1     Running   0          2d17h

再次查看是否獲取到監控指標

1.8+]# kubectl  top node
NAME     CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%
master   429m         10%    1605Mi          43%
node1    162m         4%     691Mi           18%
node2    154m         3%     753Mi           20%
1.8+]# kubectl  top pod -A
NAMESPACE              NAME                                             CPU(cores)   MEMORY(bytes)
kube-system            coredns-6bcbd68c66-9j6sx                         8m           12Mi
kube-system            coredns-6bcbd68c66-9mjck                         5m           7Mi
kube-system            etcd-master                                      23m          168Mi
kube-system            kube-apiserver-master                            75m          309Mi
kube-system            kube-controller-manager-master                   32m          45Mi
kube-system            kube-flannel-ds-64qdh                            4m           42Mi
kube-system            kube-flannel-ds-d2g8j                            3m           47Mi
kube-system            kube-flannel-ds-qmssw                            3m           44Mi
kube-system            kube-proxy-4vkl5                                 1m           20Mi
kube-system            kube-proxy-mls6g                                 1m           18Mi
kube-system            kube-proxy-t4xmg                                 2m           20Mi
kube-system            kube-scheduler-master                            6m           20Mi
kube-system            metrics-server-d8669575f-xl6mw                   3m           14Mi
kubernetes-dashboard   dashboard-metrics-scraper-7b8b58dc8b-757sw       1m           17Mi
kubernetes-dashboard   kubernetes-dashboard-75fdb885bf-f29ng            4m           17Mi


免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。



猜您在找 啟用k8s metrics server監控 k8s安裝metrics-server k8s安裝metrics-server K8S 安裝 metrics-server v0.3.7 k8s之資源指標API部署metrics-server k8s全棧監控之metrics-server和prometheus K8S部署Metrics-Server服務 k8s搭建監控：安裝metrics server和dashboard K8S部署Metrics-Server服務 k8s 自帶監控metrics-server
 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM