diff options
| author | Paul Buetow <paul@buetow.org> | 2026-03-28 00:01:58 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-03-28 00:01:58 +0200 |
| commit | 3a0ba6e9e7620434eac37e5ef39cb9874a209e72 (patch) | |
| tree | 275ed6d1c880bd5b9ba317a5e0b8fc3d8937d9c4 /gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi | |
| parent | fbf1da96a6674b8709a6d2aa9cf65f5af8a2195a (diff) | |
Update content for gemtext
Diffstat (limited to 'gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi')
| -rw-r--r-- | gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi index fb67c3a2..8e7c7d01 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi @@ -127,7 +127,7 @@ Power outages are regularly in my area, so a UPS keeps the infrastructure runnin ## Monitoring: Keeping an eye on everything -Robust monitoring is vital to any infrastructure, especially one as distributed as mine. I've thought about a setup that ensures I'll always be aware of what's happening in my environment. +I want to know when stuff breaks (ideally before it breaks), so monitoring is a big part of the plan. ### Prometheus and Grafana @@ -135,7 +135,7 @@ Inside the k3s cluster, Prometheus will be deployed to handle metrics collection => https://prometheus.io -For visualization, Grafana will be deployed alongside Prometheus. Grafana lets me build dynamic, customizable dashboards that provide a real-time view of everything from resource utilization to application performance. Whether it's keeping track of CPU load, memory usage, or the health of Kubernetes pods, Grafana has it covered. This will also make troubleshooting easier, as I can quickly pinpoint where issues are arising. +For visualization, Grafana will be deployed alongside Prometheus. I mostly just want dashboards for CPU, memory, and pod health — the usual stuff. Makes it way easier to figure out what's going wrong when something inevitably does. => https://grafana.com @@ -156,7 +156,7 @@ This setup may be just the beginning. Some ideas I'm thinking about for the futu For now, though, I'm focused on completing the migration from AWS ECS and getting all my Docker containers running smoothly in k3s. -What's your take on self-hosting? Are you planning to move away from managed cloud services? Stay tuned for the second part of this series, where I will likely write about the hardware and the OS setups. +Anyway, stay tuned — in part 2 I'll probably get into the hardware and OS setup. Read the next post of this series: |