joeac/joeac.net
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: joeac/joeac.net:aad796740278d9954cef442cf92c59aa65fe5cfd
Branches Tags
joeac/joeac.net:main
..
compare: joeac/joeac.net:f27a25fdf5954a18f418ec8f4e3ff79bbc8fa333
Branches Tags
joeac/joeac.net:main

2 Commits
aad7967402 .. f27a25fdf5

Author SHA1 Message Date
joeac f27a25fdf5 Merge branch 'main' of https://git.joeac.net/joeac/joeac.net 2026-06-30 16:20:24 +01:00
joeac 0181a703f9 add microlog post 2026-06-30 2026-06-30 16:20:20 +01:00
1 changed files with 7 additions and 0 deletions
Expand all files Collapse all files
common/microlog/2026-06-30.gmi
+7
View File
@@ -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.