容器雲平臺No.7~kubernetes監控系統prometheus-operator
簡介
prometheus-operator
Prometheus：一個很是優秀的監控工具或者說是監控方案。它提供了數據蒐集、存儲、處理、可視化和告警一套完整的解決方案。做爲kubernetes官方推薦的監控系統，用Prometheus來監控kubernetes集羣的情況和運行在集羣上的應用運行情況。node
Prometheus架構圖
linux
那Prometheus Operator是作什麼的呢？
Operator是由CoreOS公司開發的，用來擴展 Kubernetes API，特定的應用程序控制器，它用來建立、配置和管理複雜的有狀態應用，如數據庫、緩存和監控系統。
能夠理解爲，Prometheus Operator就是用於管理部署Prometheus到kubernetes的工具，其目的是簡化和自動化對Prometheus組件的維護。git
Prometheus Operator架構github
部署前準備
一、克隆kube-prometheus項目數據庫
[root@k8s-master001 opt]# git clone https://github.com/prometheus-operator/kube-prometheus.git
二、進入kube-prometheus/manifests目錄，能夠看到一堆yaml文件，文件太多，咱們按用組件分類vim
[root@k8s-master001 manifests]# ls -al total 20 drwxr-xr-x. 10 root root 140 Sep 14 21:25 . drwxr-xr-x. 12 root root 4096 Sep 14 21:11 .. drwxr-xr-x. 2 root root 4096 Sep 14 21:23 adapter drwxr-xr-x. 2 root root 189 Sep 14 21:22 alertmanager drwxr-xr-x. 2 root root 241 Sep 14 21:22 exporter drwxr-xr-x. 2 root root 254 Sep 14 21:23 grafana drwxr-xr-x. 2 root root 272 Sep 14 21:22 metrics drwxr-xr-x. 2 root root 4096 Sep 14 21:25 prometheus drwxr-xr-x. 2 root root 4096 Sep 14 21:23 serviceMonitor drwxr-xr-x. 2 root root 4096 Sep 14 21:11 setup
三、修改yaml文件中的nodeSelector
首先查看下如今Node節點的標籤api
[root@k8s-master001 manifests]# kubectl get node --show-labels=true NAME STATUS ROLES AGE VERSION LABELS k8s-master001 Ready master 4d16h v1.19.0 app.storage=rook-ceph,beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=k8s-master001,kubernetes.io/os=linux,node-role.kubernetes.io/master= k8s-master002 Ready master 4d16h v1.19.0 app.storage=rook-ceph,beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=k8s-master002,kubernetes.io/os=linux,node-role.kubernetes.io/master= k8s-master003 Ready master 4d16h v1.19.0 app.storage=rook-ceph,beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=k8s-master003,kubernetes.io/os=linux,node-role.kubernetes.io/master=,role=ingress-controller
並把manifests目錄的yaml文件中nodeSelector改成kubernetes.io/os=linux
例如：vim setup/prometheus-operator-deployment.yaml，瀏覽器
nodeSelector:
kubernetes.io/os: linux
其餘的自行修改,能夠以下命令過濾並查看是否須要修改緩存
[root@k8s-master001 manifests]# grep -A1 nodeSelector prometheus/* prometheus/prometheus-prometheus.yaml: nodeSelector: prometheus/prometheus-prometheus.yaml: nodeSelector: prometheus/prometheus-prometheus.yaml- kubernetes.io/os: linux
部署kube-prometheus
一、安裝operatorbash
[root@k8s-master001 manifests]# kubectl apply -f setup/ namespace/monitoring created customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created clusterrole.rbac.authorization.k8s.io/prometheus-operator created clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator created deployment.apps/prometheus-operator created service/prometheus-operator created serviceaccount/prometheus-operator created [root@k8s-master001 manifests]# kubectl get po -n monitoring NAME READY STATUS RESTARTS AGE prometheus-operator-74d54b5cfc-xgqg7 2/2 Running 0 2m40s
二、安裝adapter
[root@k8s-master001 manifests]# kubectl apply -f adapter/ apiservice.apiregistration.k8s.io/v1beta1.metrics.k8s.io created clusterrole.rbac.authorization.k8s.io/prometheus-adapter created clusterrole.rbac.authorization.k8s.io/system:aggregated-metrics-reader created clusterrolebinding.rbac.authorization.k8s.io/prometheus-adapter created clusterrolebinding.rbac.authorization.k8s.io/resource-metrics:system:auth-delegator created clusterrole.rbac.authorization.k8s.io/resource-metrics-server-resources created configmap/adapter-config created deployment.apps/prometheus-adapter created rolebinding.rbac.authorization.k8s.io/resource-metrics-auth-reader created service/prometheus-adapter created serviceaccount/prometheus-adapter created servicemonitor.monitoring.coreos.com/prometheus-adapter created [root@k8s-master001 manifests]# kubectl get po -n monitoring NAME READY STATUS RESTARTS AGE prometheus-adapter-557648f58c-9x446 1/1 Running 0 41s prometheus-operator-74d54b5cfc-xgqg7 2/2 Running 0 4m33s
三、安裝alertmanager
[root@k8s-master001 manifests]# kubectl apply -f alertmanager/ alertmanager.monitoring.coreos.com/main created secret/alertmanager-main created service/alertmanager-main created serviceaccount/alertmanager-main created servicemonitor.monitoring.coreos.com/alertmanager created [root@k8s-master001 ~]# kubectl get po -n monitoring NAME READY STATUS RESTARTS AGE alertmanager-main-0 2/2 Running 0 53m alertmanager-main-1 2/2 Running 0 3m3s alertmanager-main-2 2/2 Running 0 53m
四、安裝exporter
[root@k8s-master001 manifests]# kubectl apply -f exporter/ clusterrole.rbac.authorization.k8s.io/node-exporter created clusterrolebinding.rbac.authorization.k8s.io/node-exporter created daemonset.apps/node-exporter created service/node-exporter created serviceaccount/node-exporter created servicemonitor.monitoring.coreos.com/node-exporter created [root@k8s-master001 manifests]# kubectl get po -n monitoring NAME READY STATUS RESTARTS AGE node-exporter-2rvtt 2/2 Running 0 108s node-exporter-9kwb6 2/2 Running 0 108s node-exporter-9zlbb 2/2 Running 0 108s
五、安裝metrics
[root@k8s-master001 manifests]# kubectl apply -f metrics clusterrole.rbac.authorization.k8s.io/kube-state-metrics created clusterrolebinding.rbac.authorization.k8s.io/kube-state-metrics created deployment.apps/kube-state-metrics created service/kube-state-metrics created serviceaccount/kube-state-metrics created servicemonitor.monitoring.coreos.com/kube-state-metrics created [root@k8s-master001 manifests]# kubectl get po -n monitoring NAME READY STATUS RESTARTS AGE kube-state-metrics-85cb9cfd7c-v9c4f 3/3 Running 0 2m8s
六、安裝prometheus
[root@k8s-master001 manifests]# kubectl apply -f prometheus/ clusterrole.rbac.authorization.k8s.io/prometheus-k8s created clusterrolebinding.rbac.authorization.k8s.io/prometheus-k8s created servicemonitor.monitoring.coreos.com/prometheus-operator created prometheus.monitoring.coreos.com/k8s created rolebinding.rbac.authorization.k8s.io/prometheus-k8s-config created rolebinding.rbac.authorization.k8s.io/prometheus-k8s created rolebinding.rbac.authorization.k8s.io/prometheus-k8s created rolebinding.rbac.authorization.k8s.io/prometheus-k8s created role.rbac.authorization.k8s.io/prometheus-k8s-config created role.rbac.authorization.k8s.io/prometheus-k8s created role.rbac.authorization.k8s.io/prometheus-k8s created role.rbac.authorization.k8s.io/prometheus-k8s created prometheusrule.monitoring.coreos.com/prometheus-k8s-rules created service/prometheus-k8s created serviceaccount/prometheus-k8s created [root@k8s-master001 manifests]# kubectl get po -n monitoring NAME READY STATUS RESTARTS AGE prometheus-k8s-0 3/3 Running 1 94s prometheus-k8s-1 3/3 Running 1 94s
七、安裝grafana
root@k8s-master001 manifests]# kubectl apply -f grafana/ secret/grafana-datasources created configmap/grafana-dashboard-apiserver created configmap/grafana-dashboard-cluster-total created configmap/grafana-dashboard-controller-manager created configmap/grafana-dashboard-k8s-resources-cluster created configmap/grafana-dashboard-k8s-resources-namespace created configmap/grafana-dashboard-k8s-resources-node created configmap/grafana-dashboard-k8s-resources-pod created configmap/grafana-dashboard-k8s-resources-workload created configmap/grafana-dashboard-k8s-resources-workloads-namespace created configmap/grafana-dashboard-kubelet created configmap/grafana-dashboard-namespace-by-pod created configmap/grafana-dashboard-namespace-by-workload created configmap/grafana-dashboard-node-cluster-rsrc-use created configmap/grafana-dashboard-node-rsrc-use created configmap/grafana-dashboard-nodes created configmap/grafana-dashboard-persistentvolumesusage created configmap/grafana-dashboard-pod-total created configmap/grafana-dashboard-prometheus-remote-write created configmap/grafana-dashboard-prometheus created configmap/grafana-dashboard-proxy created configmap/grafana-dashboard-scheduler created configmap/grafana-dashboard-statefulset created configmap/grafana-dashboard-workload-total created configmap/grafana-dashboards created deployment.apps/grafana created service/grafana created serviceaccount/grafana created servicemonitor.monitoring.coreos.com/grafana created [root@k8s-master001 manifests]# kubectl get po -n monitoring NAME READY STATUS RESTARTS AGE grafana-b558fb99f-87spq 1/1 Running 0 3m14s
八、安裝serviceMonitor
[root@k8s-master001 manifests]# kubectl apply -f serviceMonitor/ servicemonitor.monitoring.coreos.com/prometheus created servicemonitor.monitoring.coreos.com/kube-apiserver created servicemonitor.monitoring.coreos.com/coredns created servicemonitor.monitoring.coreos.com/kube-controller-manager created servicemonitor.monitoring.coreos.com/kube-scheduler created servicemonitor.monitoring.coreos.com/kubelet created
九、查看所有運行的服務
[root@k8s-master001 manifests]# kubectl get po -n monitoring NAME READY STATUS RESTARTS AGE alertmanager-main-0 2/2 Running 0 90m alertmanager-main-1 2/2 Running 0 40m alertmanager-main-2 2/2 Running 0 90m grafana-b558fb99f-87spq 1/1 Running 0 4m56s kube-state-metrics-85cb9cfd7c-v9c4f 3/3 Running 0 10m node-exporter-2rvtt 2/2 Running 0 35m node-exporter-9kwb6 2/2 Running 0 35m node-exporter-9zlbb 2/2 Running 0 35m prometheus-adapter-557648f58c-9x446 1/1 Running 0 91m prometheus-k8s-0 3/3 Running 1 7m49s prometheus-k8s-1 3/3 Running 1 7m49s prometheus-operator-74d54b5cfc-xgqg7 2/2 Running 0 95m NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/alertmanager-main ClusterIP 10.98.96.94 <none> 9093/TCP 91m service/alertmanager-operated ClusterIP None <none> 9093/TCP,9094/TCP,9094/UDP 91m service/grafana ClusterIP 10.108.204.33 <none> 3000/TCP 6m30s service/kube-state-metrics ClusterIP None <none> 8443/TCP,9443/TCP 12m service/node-exporter ClusterIP None <none> 9100/TCP 36m service/prometheus-adapter ClusterIP 10.98.16.117 <none> 443/TCP 93m service/prometheus-k8s ClusterIP 10.109.119.37 <none> 9090/TCP 9m22s service/prometheus-operated ClusterIP None <none> 9090/TCP 9m24s service/prometheus-operator ClusterIP None <none> 8443/TCP 97m
十、使用nodeport暴露grafana和prometheus服務，訪問UI界面
---
apiVersion: v1
kind: Service
metadata:
name: grafana-svc
namespace: monitoring
spec:
type: NodePort
ports:
- port: 3000
targetPort: 3000
selector:
app: grafana
---
apiVersion: v1
kind: Service
metadata:
name: prometheus-svc
namespace: monitoring
spec:
type: NodePort
ports:
- port: 9090
targetPort: 9090
selector:
prometheus: k8s
查看結果
[root@k8s-master001 manifests]# kubectl get svc -n monitoring NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE grafana-svc NodePort 10.99.31.100 <none> 3000:30438/TCP 9s prometheus-svc NodePort 10.102.245.8 <none> 9090:32227/TCP 3s
如今能夠使用瀏覽器訪問URL NodeIP:30438 NodeIP:32227 : NodeIP爲k8s節點IP，固然也能夠使用前文介紹的ingress暴露服務
例如：
prometheus： http://10.26.25.20:32227
grafana： http://10.26.25.20:30438 默認密碼admin/admin,登陸後須要修改admin密碼
以上，kube-prometheus已經部署完畢，能夠用過prometheus查看到監控信息了。
幾個小坑
坑位一
一、從prometheus target能夠看到，kube-controller-manager和kube-scheduler都沒有被監控
解決
這是由於serviceMonitor是根據label去選取svc的,咱們能夠看到對應的serviceMonitor是選取的namespace範圍是kube-system
[root@k8s-master001 manifests]# grep -A2 -B2 selector serviceMonitor/prometheus-serviceMonitorKube* serviceMonitor/prometheus-serviceMonitorKubeControllerManager.yaml- matchNames: serviceMonitor/prometheus-serviceMonitorKubeControllerManager.yaml- - kube-system serviceMonitor/prometheus-serviceMonitorKubeControllerManager.yaml: selector: serviceMonitor/prometheus-serviceMonitorKubeControllerManager.yaml- matchLabels: serviceMonitor/prometheus-serviceMonitorKubeControllerManager.yaml- k8s-app: kube-controller-manager -- serviceMonitor/prometheus-serviceMonitorKubelet.yaml- matchNames: serviceMonitor/prometheus-serviceMonitorKubelet.yaml- - kube-system serviceMonitor/prometheus-serviceMonitorKubelet.yaml: selector: serviceMonitor/prometheus-serviceMonitorKubelet.yaml- matchLabels: serviceMonitor/prometheus-serviceMonitorKubelet.yaml- k8s-app: kubelet -- serviceMonitor/prometheus-serviceMonitorKubeScheduler.yaml- matchNames: serviceMonitor/prometheus-serviceMonitorKubeScheduler.yaml- - kube-system serviceMonitor/prometheus-serviceMonitorKubeScheduler.yaml: selector: serviceMonitor/prometheus-serviceMonitorKubeScheduler.yaml- matchLabels: serviceMonitor/prometheus-serviceMonitorKubeScheduler.yaml- k8s-app: kube-scheduler
二、建立kube-controller-manager和kube-scheduler service
k8s v1.19默認使用https，kube-controller-manager端口10257 kube-scheduler端口10259
kube-controller-manager-scheduler.yml
apiVersion: v1
kind: Service
metadata:
namespace: kube-system
name: kube-controller-manager
labels:
k8s-app: kube-controller-manager
spec:
selector:
component: kube-controller-manager
type: ClusterIP
clusterIP: None
ports:
- name: https-metrics
port: 10257
targetPort: 10257
protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
namespace: kube-system
name: kube-scheduler
labels:
k8s-app: kube-scheduler
spec:
selector:
component: kube-scheduler
type: ClusterIP
clusterIP: None
ports:
- name: https-metrics
port: 10259
targetPort: 10259
protocol: TCP
執行命令
[root@k8s-master001 manifests]# kubectl apply -f kube-controller-manager-scheduler.yml [root@k8s-master001 manifests]# kubectl get svc -n kube-system NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kube-controller-manager ClusterIP None <none> 10257/TCP 37m kube-scheduler ClusterIP None <none> 10259/TCP 37m
三、建立kube-controller-manager和kube-scheduler endpoint
注意：addresses改爲集羣實際的IP
kube-ep.yml
apiVersion: v1
kind: Endpoints
metadata:
labels:
k8s-app: kube-controller-manager
name: kube-controller-manager
namespace: kube-system
subsets:
- addresses:
- ip: 10.26.25.20
- ip: 10.26.25.21
- ip: 10.26.25.22
ports:
- name: https-metrics
port: 10257
protocol: TCP
---
apiVersion: v1
kind: Endpoints
metadata:
labels:
k8s-app: kube-scheduler
name: kube-scheduler
namespace: kube-system
subsets:
- addresses:
- ip: 10.26.25.20
- ip: 10.26.25.21
- ip: 10.26.25.22
ports:
- name: https-metrics
port: 10259
protocol: TCP
[root@k8s-master001 manifests]# kubectl apply -f kube-ep.yml endpoints/kube-controller-manager created endpoints/kube-scheduler created [root@k8s-master001 manifests]# kubectl get ep -n kube-system NAME ENDPOINTS AGE kube-controller-manager 10.26.25.20:10257,10.26.25.21:10257,10.26.25.22:10257 16m kube-scheduler 10.26.25.20:10259,10.26.25.21:10259,10.26.25.22:10259 16m
如今看下頁面上prometheus target，已經能看到kube-controller-manager和kube-scheduler被監控了
坑位二
一、默認清理下，kube-controller-manager和kube-scheduler綁定IP爲127.0.0.1，若是須要監控這兩個服務，須要修改kube-controller-manager和kube-scheduler配置，讓其綁定到0.0.0.0
二、配置文件所在目錄/etc/kubernetes/manifests
修改kube-controller-manager.yaml中--bind-address=0.0.0.0
修改kube-scheduler.yaml中--bind-address=0.0.0.0
三、重啓kubelet:systemctl restart kubelet
四、查看是否生效，返回200即爲成功
[root@k8s-master002 manifests]# curl -I -k https://10.26.25.20:10257/healthz HTTP/1.1 200 OK Cache-Control: no-cache, private Content-Type: text/plain; charset=utf-8 X-Content-Type-Options: nosniff Date: Tue, 15 Sep 2020 06:19:32 GMT Content-Length: 2 [root@k8s-master002 manifests]# curl -I -k https://10.26.25.20:10259/healthz HTTP/1.1 200 OK Cache-Control: no-cache, private Content-Type: text/plain; charset=utf-8 X-Content-Type-Options: nosniff Date: Tue, 15 Sep 2020 06:19:36 GMT Content-Length: 2
最後
kube-prometheus配置不少，這裏只是作了最基礎的設置。更多需求請自行查看官方文檔
注：文中圖片來源於網絡，若有侵權，請聯繫我及時刪除。