k3s: Pod-Monitoring in Grafana (Task 6.5)

kube-state-metrics (NodePort 30808) und ServiceAccount prometheus-infra (nur
nodes/metrics) im Cluster; Prometheus auf infra liest kubelet/cAdvisor per TLS
gegen die k3s-CA. Ziele per file_sd aus kubectl get nodes, cAdvisor auf die
nötigen Reihen begrenzt. Dashboard "k3s – Pods" (Vorgabe nex), Alerts K3s*
nur mit notify. Playbook monitoring-k3s.yml.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

config/healer-rules.yaml

@@ -51,3 +51,24 @@ rules:
     match: {alertname: DiskAlmostFull}
     ladder:
       - {action: notify, params: {text: "Platte auf {instance} ({mountpoint}) fast voll", severity: warning}, attempts: 1}
+
+  # k3s (Task 6.5): nur melden; Pods startet Kubernetes selbst neu
+  - id: k3s-node-not-ready
+    match: {alertname: K3sNodeNotReady}
+    ladder:
+      - {action: notify, params: {text: "k3s-Knoten {node} nicht bereit – VM und k3s-agent prüfen", severity: high}, attempts: 1}
+
+  - id: k3s-pod-crashloop
+    match: {alertname: K3sPodCrashLooping}
+    ladder:
+      - {action: notify, params: {text: "Pod {namespace}/{pod} ({container}) startet immer wieder neu", severity: warning}, attempts: 1}
+
+  - id: k3s-deployment-unavailable
+    match: {alertname: K3sDeploymentUnavailable}
+    ladder:
+      - {action: notify, params: {text: "Deployment {namespace}/{deployment} hat zu wenige bereite Pods", severity: warning}, attempts: 1}
+
+  - id: k3s-memory-near-limit
+    match: {alertname: K3sContainerMemoryNearLimit}
+    ladder:
+      - {action: notify, params: {text: "{namespace}/{pod} ({container}) über 90 % des Speicherlimits", severity: warning}, attempts: 1}