Update content for md

3 files changed, 25 insertions, 2 deletions

diff --git a/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.md b/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.md
index 43ab1446..8e74c198 100644
--- a/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.md
+++ b/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.md
@@ -68,7 +68,7 @@ $ cd f3s/
 - Additional resources under `*/manifests/` directories (e.g., `prometheus/manifests/`)
 - Justfiles updated to trigger ArgoCD syncs instead of direct Helm commands
 
-The deployment concepts and architecture remain the same—only the deployment method changed from imperative (`helm install/upgrade`) to declarative (GitOps with ArgoCD). For details on the GitOps migration, see Part X of this series.
+The deployment concepts and architecture remain the same—only the deployment method changed from imperative (`helm install/upgrade`) to declarative (GitOps with ArgoCD).
 
 ## Updating
 
diff --git a/gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md b/gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md
index 1f61e325..ef31a79e 100644
--- a/gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md
+++ b/gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md
@@ -80,7 +80,7 @@ $ cd f3s/prometheus/
 - Resources organized under `prometheus/manifests/`, `loki/`, etc.
 - Justfiles updated to trigger ArgoCD syncs instead of direct Helm commands
 
-The deployment concepts and architecture remain the same—only the deployment method changed from imperative (`helm install/upgrade`) to declarative (GitOps with ArgoCD). For details on the GitOps migration, see Part X of this series. 
+The deployment concepts and architecture remain the same—only the deployment method changed from imperative (`helm install/upgrade`) to declarative (GitOps with ArgoCD). 
 
 ## Persistent storage recap
 
diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8b.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8b.md
index 321104ff..99db0e9d 100644
--- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8b.md
+++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8b.md
@@ -6,6 +6,29 @@ This post covers enabling etcd metrics monitoring for the k3s cluster. The etcd
 
 [Part 8: Observability](./2025-12-07-f3s-kubernetes-with-freebsd-part-8.html)  
 
+## Important Note: GitOps Migration
+
+**Note:** After the initial observability setup, the f3s cluster was migrated from imperative Helm deployments to declarative GitOps using ArgoCD. The Prometheus configuration and deployment process described in this post have been updated for ArgoCD.
+
+**To view the configuration as it existed before the ArgoCD migration**, check out the pre-ArgoCD revision:
+
+```sh
+$ git clone https://codeberg.org/snonux/conf.git
+$ cd conf
+$ git checkout 15a86f3  # Last commit before ArgoCD migration
+$ cd f3s/prometheus/
+```
+
+**Current master branch** uses ArgoCD with:
+- Application manifest: `argocd-apps/monitoring/prometheus.yaml`
+- Multi-source Application combining upstream chart + custom manifests
+- Justfile commands updated to trigger ArgoCD syncs instead of direct Helm commands
+
+The etcd configuration concepts remain the same—only the deployment method changed. Instead of running `just upgrade`, you would:
+1. Update the configuration in Git
+2. Commit and push
+3. ArgoCD automatically syncs (or run `just sync` for immediate sync)
+
 ## Enabling etcd metrics in k3s
 
 On each control-plane node (r0, r1, r2), create /etc/rancher/k3s/config.yaml: