From b0db3b60b6ae9af899bb7a189919e1601ac2a7ab Mon Sep 17 00:00:00 2001
From: Paul Buetow <paul@buetow.org>
Date: Fri, 26 Dec 2025 23:35:10 +0200
Subject: Update content for md

---
 ...025-07-14-f3s-kubernetes-with-freebsd-part-6.md |  11 +-
 ...ubernetes-with-freebsd-part-X-OBSERVABILITY2.md | 131 +++++++++++++++++++++
 2 files changed, 140 insertions(+), 2 deletions(-)
 create mode 100644 gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.md

(limited to 'gemfeed')

diff --git a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md
index 3dc754bb..83b8eb9c 100644
--- a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md
+++ b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.md
@@ -1543,10 +1543,17 @@ Domain = lan.buetow.org
 .
 ```
 
-And afterwards, we need to run the following on all 3 Rocky hosts::
+We also need to increase the inotify limit, otherwise nfs-idmapd may fail to start with "Too many open files":
 
 ```sh
-[root@r0 ~]# systemctl enable --now nfs-idmapd
+[root@r0 ~]# echo 'fs.inotify.max_user_instances = 512' > /etc/sysctl.d/99-inotify.conf
+[root@r0 ~]# sysctl -w fs.inotify.max_user_instances=512
+```
+
+And afterwards, we need to run the following on all 3 Rocky hosts:
+
+```sh
+[root@r0 ~]# systemctl start nfs-idmapd
 [root@r0 ~]# systemctl enable --now nfs-client.target
 ```
 
diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.md
new file mode 100644
index 00000000..0f7753eb
--- /dev/null
+++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.md
@@ -0,0 +1,131 @@
+# f3s: Kubernetes with FreeBSD - Part 9: Enabling etcd Metrics
+
+## Introduction
+
+This post covers enabling etcd metrics monitoring for the k3s cluster. The etcd dashboard in Grafana initially showed no data because k3s uses an embedded etcd that doesn't expose metrics by default.
+
+[Part 8: Observability](./2025-12-07-f3s-kubernetes-with-freebsd-part-8.html)  
+
+## Enabling etcd metrics in k3s
+
+On each control-plane node (r0, r1, r2), create /etc/rancher/k3s/config.yaml:
+
+```
+etcd-expose-metrics: true
+```
+
+Then restart k3s on each node:
+
+```
+systemctl restart k3s
+```
+
+After restarting, etcd metrics are available on port 2381:
+
+```
+curl http://127.0.0.1:2381/metrics | grep etcd
+```
+
+## Configuring Prometheus to scrape etcd
+
+In persistence-values.yaml, enable kubeEtcd with the node IP addresses:
+
+```
+kubeEtcd:
+  enabled: true
+  endpoints:
+    - 192.168.1.120
+    - 192.168.1.121
+    - 192.168.1.122
+  service:
+    enabled: true
+    port: 2381
+    targetPort: 2381
+```
+
+Apply the changes:
+
+```
+just upgrade
+```
+
+## Verifying etcd metrics
+
+After the changes, all etcd targets are being scraped:
+
+```
+kubectl exec -n monitoring prometheus-prometheus-kube-prometheus-prometheus-0 \
+  -c prometheus -- wget -qO- 'http://localhost:9090/api/v1/query?query=etcd_server_has_leader' | \
+  jq -r '.data.result[] | "\(.metric.instance): \(.value[1])"'
+```
+
+Output:
+
+```
+192.168.1.120:2381: 1
+192.168.1.121:2381: 1
+192.168.1.122:2381: 1
+```
+
+The etcd dashboard in Grafana now displays metrics including Raft proposals, leader elections, and peer round trip times.
+
+## Complete persistence-values.yaml
+
+The complete updated persistence-values.yaml:
+
+```
+kubeEtcd:
+  enabled: true
+  endpoints:
+    - 192.168.1.120
+    - 192.168.1.121
+    - 192.168.1.122
+  service:
+    enabled: true
+    port: 2381
+    targetPort: 2381
+
+prometheus:
+  prometheusSpec:
+    additionalScrapeConfigsSecret:
+      enabled: true
+      name: additional-scrape-configs
+      key: additional-scrape-configs.yaml
+    storageSpec:
+      volumeClaimTemplate:
+        spec:
+          storageClassName: ""
+          accessModes: ["ReadWriteOnce"]
+          resources:
+            requests:
+              storage: 10Gi
+          selector:
+            matchLabels:
+              type: local
+              app: prometheus
+
+grafana:
+  persistence:
+    enabled: true
+    type: pvc
+    existingClaim: "grafana-data-pvc"
+
+  initChownData:
+    enabled: false
+
+  podSecurityContext:
+    fsGroup: 911
+    runAsUser: 911
+    runAsGroup: 911
+```
+
+## Summary
+
+Enabled etcd metrics monitoring for the k3s embedded etcd by:
+
+* Adding etcd-expose-metrics: true to /etc/rancher/k3s/config.yaml on each control-plane node
+* Configuring Prometheus to scrape etcd on port 2381
+
+The etcd dashboard now provides visibility into cluster health, leader elections, and Raft consensus metrics.
+
+[prometheus configuration on Codeberg](https://codeberg.org/snonux/conf/src/branch/master/f3s/prometheus)  
-- 
cgit v1.2.3