From 0181a703f9581f7d0b896c9d265a642a660fbdbd Mon Sep 17 00:00:00 2001 From: Joe Carstairs Date: Tue, 30 Jun 2026 16:20:20 +0100 Subject: [PATCH] add microlog post 2026-06-30 --- common/microlog/2026-06-30.gmi | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 common/microlog/2026-06-30.gmi diff --git a/common/microlog/2026-06-30.gmi b/common/microlog/2026-06-30.gmi new file mode 100644 index 0000000..1c6dec8 --- /dev/null +++ b/common/microlog/2026-06-30.gmi @@ -0,0 +1,7 @@ +So I've now got half a dozen services running on my homelab across two machines. I need to install the services on each machine, keep them running after crashes and reboots, update and restart them when the source code changes, and co-ordinate them with each other (since I can only have one public IP on my home network, but I want to serve stuff over the Internet from both machines). + +I am currently managing this with Podman, some Dockerfiles and Docker-Compose files, Makefiles, and a lot of manual interference. This just about works, and is probably reasonably sensible for the small, low-consequence situation. + +Still, it is a faff. I'm wondering: is this kind of what Kubernetes is for? I've never understood. Looking at the documentation, I find it really hard to understand what Kubernetes is for. Maybe it's for situations kind of like this (only typically much bigger)? + +Answers on a postcard please.