From fc3af3dee40c986238cfa5ad07669c05d340560c Mon Sep 17 00:00:00 2001
From: baschno <bastian.schnorbus@gmail.com>
Date: Sat, 28 Dec 2024 19:50:13 +0100
Subject: [PATCH] prom install

---
 prometheus-stack/README.md                    |  29 ++++
 .../kube-prometheus-stack-values.yaml         | 162 ++++++++++++++++++
 2 files changed, 191 insertions(+)
 create mode 100644 prometheus-stack/README.md
 create mode 100644 prometheus-stack/kube-prometheus-stack-values.yaml

diff --git a/prometheus-stack/README.md b/prometheus-stack/README.md
new file mode 100644
index 0000000..f273413
--- /dev/null
+++ b/prometheus-stack/README.md
@@ -0,0 +1,29 @@
+
+https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack#configuration
+
+
+```
+helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
+helm repo update
+```
+
+Use for `helm` values:
+https://github.com/cablespaghetti/k3s-monitoring/blob/master/kube-prometheus-stack-values.yaml
+
+```
+helm upgrade --install prometheus prometheus-community/kube-prometheus-stack --create-namespace --namespace monitoring --values kube-prometheus-stack-values.yaml
+```
+
+Accessing UIs via PortForwarding
+```
+kubectl port-forward svc/prometheus-grafana 8080:80 -n monitoring
+kubectl port-forward svc/prometheus-kube-prometheus-prometheus 9090 -n monitoring
+kubectl port-forward svc/prometheus-kube-prometheus-alertmanager 9093 -n monitoring
+```
+
+This will make Grafana accessible on http://localhost:8080, Prometheus on http://localhost:9090 and Alert Manager on http://localhost:9093
+
+Login for Grafana:
+**User:** admin
+**Pwd:** prom-operator
+
diff --git a/prometheus-stack/kube-prometheus-stack-values.yaml b/prometheus-stack/kube-prometheus-stack-values.yaml
new file mode 100644
index 0000000..38ffef7
--- /dev/null
+++ b/prometheus-stack/kube-prometheus-stack-values.yaml
@@ -0,0 +1,162 @@
+# Disable etcd monitoring. See https://github.com/cablespaghetti/k3s-monitoring/issues/4
+kubeEtcd:
+  enabled: false
+
+# Disable kube-controller-manager and kube-scheduler monitoring. See https://github.com/cablespaghetti/k3s-monitoring/issues/2
+kubeControllerManager:
+  enabled: false
+kubeScheduler:
+  enabled: false
+
+alertmanager:
+  config:
+    global:
+      smtp_from: you@gmail.com
+      smtp_smarthost: mailhog:1025
+      smtp_require_tls: false
+    #  smtp_smarthost: smtp.gmail.com:587
+    #  smtp_auth_username: you@gmail.com
+    #  smtp_auth_password: yourapppassword # https://support.google.com/mail/answer/185833?hl=en-GB
+    #  smtp_auth_identity: you@gmail.com
+    route:
+      group_by: ['job']
+      group_wait: 30s
+      group_interval: 5m
+      repeat_interval: 1h
+      receiver: email
+      routes:
+      - match:
+          alertname: Watchdog
+        receiver: 'null'
+      - match:
+          alertname: CPUThrottlingHigh
+        receiver: 'null'
+      - match:
+          alertname: KubeMemoryOvercommit
+        receiver: 'null'
+      - match:
+          alertname: KubeCPUOvercommit
+        receiver: 'null'
+      - match:
+          alertname: KubeletTooManyPods
+        receiver: 'null'
+
+    receivers:
+    - name: 'null'
+    - name: email
+      email_configs:
+      - send_resolved: true
+        to: youremail@gmail.com
+
+    # Inhibition rules allow to mute a set of alerts given that another alert is firing.
+    # We use this to mute any warning-level notifications if the same alert is already critical.
+    inhibit_rules:
+    - source_match:
+        severity: 'critical'
+      target_match:
+        severity: 'warning'
+      # Apply inhibition if the alertname is the same.
+      equal: ['alertname', 'namespace']
+
+  alertmanagerSpec:
+#    replicas: 3
+#    podAntiAffinity: "soft"
+    storage:
+      volumeClaimTemplate:
+        spec:
+          accessModes: ["ReadWriteOnce"]
+          resources:
+            requests:
+              storage: 1Gi
+#    resources:
+#      limits:
+#        cpu: 500m
+#        memory: 64Mi
+#      requests:
+#        cpu: 25m
+#        memory: 32Mi
+#    priorityClassName: high-priority
+
+
+prometheus:
+  prometheusSpec:
+    retention: 3d
+
+#    replicas: 2
+#    podAntiAffinity: "hard"
+    storageSpec:
+      volumeClaimTemplate:
+        spec:
+          accessModes: ["ReadWriteOnce"]
+          resources:
+            requests:
+              storage: 10Gi
+
+#    resources:
+#      limits:
+#        cpu: "2"
+#        memory: 5Gi
+#      requests:
+#        cpu: 100m
+#        memory: 4Gi
+#    priorityClassName: high-priority
+#
+#  service:
+#    sessionAffinity: "ClientIP"
+#
+
+grafana:
+  plugins:
+    - grafana-piechart-panel
+#  resources:
+#    limits:
+#      cpu: 500m
+#      memory: 128Mi
+#    requests:
+#      cpu: 25m
+#      memory: 64Mi
+#
+#  sidecar:
+#    resources:
+#      limits:
+#        cpu: 100m
+#        memory: 128Mi
+#      requests:
+#        cpu: 5m
+#        memory: 64Mi
+
+#prometheusOperator:
+#  resources:
+#    limits:
+#      cpu: 1
+#      memory: 512Mi
+#    requests:
+#      cpu: 50m
+#      memory: 128Mi
+#  priorityClassName: high-priority
+
+#prometheus-node-exporter:
+#  resources:
+#    limits:
+#      cpu: 50m
+#      memory: 50Mi
+#    requests:
+#      cpu: 5m
+#      memory: 16Mi
+#  priorityClassName: high-priority
+
+kube-state-metrics:
+#  resources:
+#    limits:
+#      cpu: 1
+#      memory: 512Mi
+#    requests:
+#      cpu: 5m
+#      memory: 128Mi
+#  priorityClassName: high-priority
+
+# Use an unofficial multi-arch image until kube-state-metrics v2 is stable
+  image:
+    repository: eddiezane/kube-state-metrics
+    tag: v1.9.7
+