summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--_posts/2025-04-06-i-don-t-get-kubernetes.md38
1 files changed, 38 insertions, 0 deletions
diff --git a/_posts/2025-04-06-i-don-t-get-kubernetes.md b/_posts/2025-04-06-i-don-t-get-kubernetes.md
new file mode 100644
index 0000000..28224b4
--- /dev/null
+++ b/_posts/2025-04-06-i-don-t-get-kubernetes.md
@@ -0,0 +1,38 @@
+---
+layout: post
+title: I don't get Kubernetes
+date: 2025-04-06 15:59 +0200
+categories: tech
+lang: en
+---
+
+No real content, just me ranting.
+
+There are [some ;)](https://xeiaso.net/talks/2025/surreal-joy-homelab/) who take
+great joy in Kubernetes. I never really understood how I could use it.
+
+Okay, so, very simplified, K8s let's you say "I wanna run these services (Docker
+containers) on my cluster (various computers/servers), optionally with
+redundancy"? Well, I only have one "server" in my "homelab", and then 3 VPS or
+so. Only one of them runs something in Docker/Podman.
+
+I *can't imagine*/don't understand how I would run, say, Nextcloud in K8s. I
+*want* to know which server is currently running it, and where the data is
+stored. Especially with something like Nextcloud, I want to have the Nextcloud
+application, the database, and the data store on **one** VPS, without any
+indirections, without any communication over the internet or a VPN, via some
+proxy software. From what little I've heard about K8s (forgive me my ignorance),
+I had more questions that I could answer. K8s seems really complex, because it
+~~has~~ can have so many moving parts (yes, you can probably run a very basic
+setup, most of the components seem optional). I don't want my database suddenly
+moved around to somewhere else.
+
+That is to say: I never had a use case of trying out K8s. No *actual, real* one.
+I could probably construct one if I tried really hard. But, eh. "My current
+setup works".
+
+My attempt to run K8s on my Proxmox via LXC all failed, even if they're
+privileged containers, probably because I need to mount Linux Namespaces, or
+load specific kernel modules on Proxmox itself so they can be loaded in the LXC
+containers as well (???).
+