diff options
Diffstat (limited to 'gemfeed')
3 files changed, 6 insertions, 6 deletions
diff --git a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl index 0fa0011b..0c51334e 100644 --- a/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl +++ b/gemfeed/2025-07-14-f3s-kubernetes-with-freebsd-part-6.gmi.tpl @@ -1753,7 +1753,6 @@ MooseFS is a fault-tolerant, distributed file system that could provide proper h Both technologies could run on top of our encrypted ZFS volumes, combining ZFS's data integrity and encryption features with distributed storage capabilities. This would be particularly interesting for workloads that need either S3-compatible APIs (MinIO) or transparent distributed POSIX storage (MooseFS). What about Ceph and GlusterFS? Unfortunately, there doesn't seem to be great native FreeBSD support for them. However, other alternatives also appear suitable for my use case. - Read the next post of this series: => ./2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi f3s: Kubernetes with FreeBSD - Part 7: k3s and first pod deployments diff --git a/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl b/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl index 6d8b2ab4..98272d5b 100644 --- a/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl +++ b/gemfeed/2025-10-02-f3s-kubernetes-with-freebsd-part-7.gmi.tpl @@ -909,7 +909,9 @@ These are the charts that already live under `examples/conf/f3s` and run on the * `syncthing` — two-volume setup for config and shared data, fronted by the `syncthing.f3s.foo.zone` ingress. * `wallabag` — read-it-later service with persistent `data` and `images` directories on the NFS export. -I hope you enjoyed this walkthrough. In the next part of this series, I will likely tackle monitoring, backup, or observability. I haven't fully decided yet which topic to cover next, so stay tuned! +I hope you enjoyed this walkthrough. Read the next post of this series: + +=> ./2025-12-07-f3s-kubernetes-with-freebsd-part-8.gmi f3s: Kubernetes with FreeBSD - Part 8: Observability Other *BSD-related posts: diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8.gmi.tpl b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8.gmi.tpl index 586058a3..dc10f3ee 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8.gmi.tpl +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8.gmi.tpl @@ -4,7 +4,7 @@ This is the 8th blog post about the f3s series for my self-hosting demands in a << template::inline::index f3s-kubernetes-with-freebsd-part -=> ./f3s-kubernetes-with-freebsd-part-1f3slogo.png f3s logo +=> ./f3s-kubernetes-with-freebsd-part-1/f3slogo.png f3s logo << template::inline::toc @@ -110,8 +110,9 @@ prometheus-kube-prometheus-prometheus ClusterIP 10.43.152.163 9090/TCP,808 Grafana connects to Prometheus using the internal service URL `http://prometheus-kube-prometheus-prometheus.monitoring.svc.cluster.local:9090`. The default Grafana credentials are `admin`/`prom-operator`, which should be changed immediately after first login. +=> ./f3s-kubernetes-with-freebsd-part-8/grafana-prometheus.png Grafana dashboard showing Prometheus metrics + => ./f3s-kubernetes-with-freebsd-part-8/grafana-dashboard.png Grafana dashboard showing cluster metrics -=> ./f3s-kubernetes-with-freebsd-part-8/grafana-node-exporter.png Node Exporter dashboard with host metrics ## Installing Loki and Alloy @@ -229,8 +230,6 @@ Once configured, you can explore logs in Grafana's "Explore" view. I'll show som => ./f3s-kubernetes-with-freebsd-part-8/loki-explore.png Exploring logs in Grafana with Loki -=> ./f3s-kubernetes-with-freebsd-part-8/loki-logs-detail.png Detailed log view with parsed fields - ## The complete monitoring stack After deploying everything, here's what's running in the monitoring namespace: |