Hi everybody, I wrote this piece and it might seem a little half-baked, but I’ll never get it going if I don’t throw it out there.
Let me know what you think, thanks and selfhosting ftw.
Hi everybody, I wrote this piece and it might seem a little half-baked, but I’ll never get it going if I don’t throw it out there.
Let me know what you think, thanks and selfhosting ftw.
I’m a professional software engineer and I’ve been in the industry since before Kubernetes was first released, and I still found it overwhelming when I had to use it professionally.
I also can’t think of an instance when someone self-hosting would need it. Why did you end up looking into it?
I use Docker Compose for dozens of applications that range in complexity from “just run this service, expose it via my reverse proxy, and add my authentication middleware” to “in this stack, run this service with my custom configuration, a custom service I wrote myself or forked, and another service that I wrote a Dockerfile for; make this service accessible to this other service, but not to the reverse proxy; expose these endpoints to the auth middleware and for these endpoints, allow bypassing of the auth middleware if an API key is supplied.” And I could do much more complicated things with Docker if I needed to, so even for self-hosters with more complex use cases than mine, I question whether Kubernetes is the right fit.
Cause people online kept saying that one should use it in their homelab. It’s mentioned in basically every such post and there are a lot of videos about rpi clusters with k3s. So I assumed it’s the way to go.
I basically do the same as you but with Dokploy cause the web ui makes it easier to manage than juggling ssh terminals and remote editing textfiles in an editor from the 19th century.