31 Mar 2021
00. 사전조건 InfoKubernetes Cluster 구성 kubectl 설치 Kubernetes Config helm 설치
01. 개요 InfoKubernetes-operator Summary kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator. Installs the kube-prometheus stack , a collection of Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator . By default this chart installs additional, dependent charts:
Guide for kube-prometheus-stack with Helm3.x
02. Namespace 생성 Code Blocksansae@win10pro-worksp:$ kubectl create ns monitor-po
03. Install Chart of kube-prometheus-stack Code Blocksansae@win10pro-worksp:$ helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
"prometheus-community" already exists with the same configuration, skipping
sansae@win10pro-worksp:$
sansae@win10pro-worksp:$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "elastic" chart repository
...Successfully got an update from the "dynatrace" chart repository
...Successfully got an update from the "prometheus-community" chart repository
Update Complete. ⎈Happy Helming!⎈
sansae@win10pro-worksp:$ helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack -n monitor-po
NAME: kube-prometheus-stack
LAST DEPLOYED: Wed Mar 31 10:30:38 2021
NAMESPACE: monitor-po
STATUS: deployed
REVISION: 1
NOTES:
kube-prometheus-stack has been installed. Check its status by running:
kubectl --namespace monitor-po get pods -l "release=kube-prometheus-stack"
Visit https://github.com/prometheus-operator/kube-prometheus for instructions on how to create & configure Alertmanager and Prometheus instances using the Operator.
sansae@win10pro-worksp:$ kubectl get all -n monitor-po
NAME READY STATUS RESTARTS AGE
pod/alertmanager-kube-prometheus-stack-alertmanager-0 2/2 Running 0 91s
pod/kube-prometheus-stack-grafana-6b5c8fd86c-lwcv2 2/2 Running 0 93s
pod/kube-prometheus-stack-kube-state-metrics-7877f4cc7c-b2nnc 1/1 Running 0 93s
pod/kube-prometheus-stack-operator-5859b9c949-4n24x 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-5f4pm 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-5fbc7 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-ggj8c 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-h5cfj 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-hvpsf 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-mbt54 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-s5zd9 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-v7bsj 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-v7sts 1/1 Running 0 93s
pod/kube-prometheus-stack-prometheus-node-exporter-vnmx5 1/1 Running 0 93s
pod/prometheus-kube-prometheus-stack-prometheus-0 2/2 Running 1 91s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)
AGE
service/alertmanager-operated ClusterIP None <none> 9093/TCP,9094/TCP,9094/UDP 91s
service/kube-prometheus-stack-alertmanager ClusterIP 10.0.92.245 <none> 9093/TCP
93s
service/kube-prometheus-stack-grafana ClusterIP 10.0.240.51 <none> 80/TCP
93s
service/kube-prometheus-stack-kube-state-metrics ClusterIP 10.0.47.252 <none> 8080/TCP
93s
service/kube-prometheus-stack-operator ClusterIP 10.0.215.243 <none> 443/TCP
93s
service/kube-prometheus-stack-prometheus ClusterIP 10.0.152.193 <none> 9090/TCP
93s
service/kube-prometheus-stack-prometheus-node-exporter ClusterIP 10.0.216.169 <none> 9100/TCP
93s
service/prometheus-operated ClusterIP None <none> 9090/TCP
91s
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
daemonset.apps/kube-prometheus-stack-prometheus-node-exporter 10 10 10 10 10 <none> 93s
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/kube-prometheus-stack-grafana 1/1 1 1 93s
deployment.apps/kube-prometheus-stack-kube-state-metrics 1/1 1 1 93s
deployment.apps/kube-prometheus-stack-operator 1/1 1 1 93s
NAME DESIRED CURRENT READY AGE
replicaset.apps/kube-prometheus-stack-grafana-6b5c8fd86c 1 1 1 93s
replicaset.apps/kube-prometheus-stack-kube-state-metrics-7877f4cc7c 1 1 1 93s
replicaset.apps/kube-prometheus-stack-operator-5859b9c949 1 1 1 93s
NAME READY AGE
statefulset.apps/alertmanager-kube-prometheus-stack-alertmanager 1/1 91s
statefulset.apps/prometheus-kube-prometheus-stack-prometheus 1/1 91s
sansae@win10pro-worksp:$
04. Volume 설정 04-01. StorageClass 확인 Prometheus Stacks에서 사용가능한 StorageClass는 AzureDisk이므로 'managed-premium '을 사용해야 합니다. Code Blocksansae@win10pro-worksp:/workspaces$ kubectl get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
azurefile kubernetes.io/azure-file Delete Immediate true 65d
azurefile-premium kubernetes.io/azure-file Delete Immediate true 65d
default (default) kubernetes.io/azure-disk Delete Immediate true 65d
managed kubernetes.io/azure-disk Delete WaitForFirstConsumer true 30d
managed-premium kubernetes.io/azure-disk Delete Immediate true 65d
04-02. Prometheus Volume Prometheus의 storage에 storageClassName: managed-premium를 추가 합니다. storage 사이즈도 프로젝트스펙에 맞게 적절하게 수정 합니다. Code Blocksansae@win10pro-worksp:/workspaces$ kubectl edit prometheus kube-prometheus-stack-prometheus -n monitor-po
=============================================================
156 storage:
157 volumeClaimTemplate:
158 spec:
159 accessModes:
160 - ReadWriteOnce
161 resources:
162 requests:
163 storage: 50Gi
164 storageClassName: managed-premium
=============================================================
prometheus.monitoring.coreos.com/kube-prometheus-stack-prometheus edited
04-03. Alertmanager Volume Alertmanager의 storage에 storageClassName: managed-premium를 추가 합니다. storage 사이즈도 프로젝트스펙에 맞게 적절하게 수정 합니다. Code Blocksansae@win10pro-worksp:/workspaces$ kubectl edit alertmanager kube-prometheus-stack-alertmanager -n monitor-po
=============================================================
85 storage:
86 volumeClaimTemplate:
87 spec:
88 storageClassName: managed-premium
89 accessModes: ["ReadWriteOnce"]
90 resources:
91 requests:
92 storage: 2Gi
=============================================================
alertmanager.monitoring.coreos.com/kube-prometheus-stack-alertmanager edited
04-04. Grafana Volume Grafana는 Prometheus-operator로 구성된 리소스가 아닙니다. 따라서, PVC를 수동으로 생성하고, Deployment에 PVC를 사용하도록 수정해 줍니다. Code Blocksansae@win10pro-worksp:/workspaces$ cat grafana-pvc.yaml
=============================================================
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: grafana-pv-claim
labels:
app: grafana
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storageClassName: managed-premium
=============================================================
sansae@win10pro-worksp:/workspaces$ kubectl create -f grafana-pvc.yaml
create pvc!!!
sansae@win10pro-worksp:/workspaces$ kubectl edit deploy kube-prometheus-stack-grafana -n monitor-po
=============================================================
400 - mountPath: /var/lib/grafana
401 name: grafana-persistent-storage
-------------------------------------------------------
453 - name: grafana-persistent-storage
454 persistentVolumeClaim:
455 claimName: grafana-pv-claim
=============================================================
deployment.apps/kube-prometheus-stack-grafana edited
05. Service Connection 05-01. Prometheus Operated Code Blocksansae@win10pro-worksp:$ kubectl get svc -n monitor-po
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
alertmanager-operated ClusterIP None <none> 9093/TCP,9094/TCP,9094/UDP 30m
kube-prometheus-stack-alertmanager ClusterIP 10.0.92.245 <none> 9093/TCP 30m
kube-prometheus-stack-grafana ClusterIP 10.0.240.51 <none> 80/TCP 30m
kube-prometheus-stack-kube-state-metrics ClusterIP 10.0.47.252 <none> 8080/TCP 30m
kube-prometheus-stack-operator ClusterIP 10.0.215.243 <none> 443/TCP 30m
kube-prometheus-stack-prometheus ClusterIP 10.0.152.193 <none> 9090/TCP 30m
kube-prometheus-stack-prometheus-node-exporter ClusterIP 10.0.216.169 <none> 9100/TCP 30m
prometheus-operated ClusterIP None <none> 9090/TCP 30m
sansae@win10pro-worksp:$ kubectl port-forward service/prometheus-operated 9090 -n monitor-po
Forwarding from 127.0.0.1:9090 -> 9090
Forwarding from [::1]:9090 -> 9090
05-02. Grafana Code Blocksansae@win10pro-worksp:$ kubectl port-forward service/kube-prometheus-stack-grafana 8000:80 -n monitor-po
Forwarding from 127.0.0.1:8000 -> 3000
Forwarding from [::1]:8000 -> 3000
Handling connection for 8000
default user/password is admin/prom-operator
05-03. AlertManager Code Blocksansae@win10pro-worksp:$ kubectl port-forward service/kube-prometheus-stack-alertmanager 9093:9093 -n monitor-po
Forwarding from 127.0.0.1:9093 -> 9093
Forwarding from [::1]:9093 -> 9093
참고: 삭제할 경우 namespace이외에 삭제 해야할 리소스 Code Blockkubectl delete crd alertmanagerconfigs.monitoring.coreos.com
kubectl delete crd alertmanagers.monitoring.coreos.com
kubectl delete crd podmonitors.monitoring.coreos.com
kubectl delete crd probes.monitoring.coreos.com
kubectl delete crd prometheuses.monitoring.coreos.com
kubectl delete crd prometheusrules.monitoring.coreos.com
kubectl delete crd servicemonitors.monitoring.coreos.com
kubectl delete crd thanosrulers.monitoring.coreos.com
kubectl delete clusterrole kube-prometheus-stack-grafana-clusterrole
kubectl delete clusterrole kube-prometheus-stack-kube-state-metrics
kubectl delete clusterrole kube-prometheus-stack-operator
kubectl delete clusterrole kube-prometheus-stack-operator-psp
kubectl delete clusterrole kube-prometheus-stack-prometheus
kubectl delete clusterrole kube-prometheus-stack-prometheus-psp
kubectl delete clusterrole psp-kube-prometheus-stack-kube-state-metrics
kubectl delete clusterrole psp-kube-prometheus-stack-prometheus-node-exporter
kubectl delete clusterrolebinding kube-prometheus-stack-grafana-clusterrolebinding
kubectl delete clusterrolebinding kube-prometheus-stack-kube-state-metrics
kubectl delete clusterrolebinding kube-prometheus-stack-operator
kubectl delete clusterrolebinding kube-prometheus-stack-operator-psp
kubectl delete clusterrolebinding kube-prometheus-stack-prometheus
kubectl delete clusterrolebinding kube-prometheus-stack-prometheus-psp
kubectl delete clusterrolebinding psp-kube-prometheus-stack-kube-state-metrics
kubectl delete clusterrolebinding psp-kube-prometheus-stack-prometheus-node-exporter
kubectl delete svc kube-prometheus-stack-coredns -n kube-system
kubectl delete svc kube-prometheus-stack-kube-controller-manager -n kube-system
kubectl delete svc kube-prometheus-stack-kube-etcd -n kube-system
kubectl delete svc kube-prometheus-stack-kube-proxy -n kube-system
kubectl delete svc kube-prometheus-stack-kube-scheduler -n kube-system
kubectl delete svc kube-prometheus-stack-kubelet -n kube-system
kubectl delete svc prometheus-kube-prometheus-kubelet -n kube-system
kubectl delete MutatingWebhookConfiguration kube-prometheus-stack-admission
kubectl delete ValidatingWebhookConfiguration kube-prometheus-stack-admission
참조: https://kangwoo.kr/2020/06/20/kubernetes-monitoring-3-kube-prometheus-%ec%84%a4%ec%b9%98-%ed%9b%84-%ed%95%b4%ec%95%bc-%ed%95%a0%ec%9d%bc/
...