From 21dbd8f5bade4868a3179d4a8d75ac0eb433b455 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 17 Nov 2024 09:32:39 +0200 Subject: Update content for gemtext --- ...24-11-17-f3s-kubernetes-with-freebsd-part-1.gmi | 2 +- ...1-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl | 2 +- gemfeed/atom.xml | 4 ++-- .../f3s-kubernetes-with-freebsd-part-1/f3slogo.png | Bin 317766 -> 185496 bytes 4 files changed, 4 insertions(+), 4 deletions(-) (limited to 'gemfeed') 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 575df91e..11269340 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 @@ -138,7 +138,7 @@ Ironically, I implemented Gogios to avoid using more complex alerting systems li This setup may be just the beginning. Some ideas I'm thinking about for the future: -* Adding more FreeBSD nodes (in different physical locations, maybe at my wider family's places?) for better redundancy. (HA storage then might be trickier) +* Adding more FreeBSD nodes (in different physical locations, maybe at my wider family's places? WireGuard would make it possible!) for better redundancy. (HA storage then might be trickier) * Deploying more Docker apps (data-intensive ones, like a picture gallery, my entire audiobook catalogue, or even a music server) to k3s. For now, though, I'm focused on completing the migration from AWS ECS and getting all my Docker containers running smoothly in k3s. diff --git a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl index fa4fae32..a199abcb 100644 --- a/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl +++ b/gemfeed/2024-11-17-f3s-kubernetes-with-freebsd-part-1.gmi.tpl @@ -123,7 +123,7 @@ Ironically, I implemented Gogios to avoid using more complex alerting systems li This setup may be just the beginning. Some ideas I'm thinking about for the future: -* Adding more FreeBSD nodes (in different physical locations, maybe at my wider family's places?) for better redundancy. (HA storage then might be trickier) +* Adding more FreeBSD nodes (in different physical locations, maybe at my wider family's places? WireGuard would make it possible!) for better redundancy. (HA storage then might be trickier) * Deploying more Docker apps (data-intensive ones, like a picture gallery, my entire audiobook catalogue, or even a music server) to k3s. For now, though, I'm focused on completing the migration from AWS ECS and getting all my Docker containers running smoothly in k3s. diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index e2082ebd..ddd26a62 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ - 2024-11-16T23:52:20+02:00 + 2024-11-17T09:31:43+02:00 foo.zone feed To be in the .zone! @@ -161,7 +161,7 @@ This setup may be just the beginning. Some ideas I'm thinking about for the future:


For now, though, I'm focused on completing the migration from AWS ECS and getting all my Docker containers running smoothly in k3s.
diff --git a/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png b/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png index c9eb8945..cc45b40e 100644 Binary files a/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png and b/gemfeed/f3s-kubernetes-with-freebsd-part-1/f3slogo.png differ -- cgit v1.2.3